db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yun Lee (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3853) Behaviour of setTypeMap() differs between embedded and client
Date Tue, 31 Mar 2009 13:48:03 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694116#action_12694116
] 

Yun Lee commented on DERBY-3853:
--------------------------------

Knut, thanks for your comments.  I will turn back on weekend to provide new patch adopting
your advice,:)

> Behaviour of setTypeMap() differs between embedded and client
> -------------------------------------------------------------
>
>                 Key: DERBY-3853
>                 URL: https://issues.apache.org/jira/browse/DERBY-3853
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Newcomer
>    Affects Versions: 10.5.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Yun Lee
>            Priority: Minor
>         Attachments: DERBY-3853-1.patch, DERBY-3853-1.stat
>
>
> On the embedded driver, Connection.setTypeMap() behaves like this (when the connection
is not closed):
>   - if the map argument is null, throw an SQLException with SQLState XJ081
>   - if the map is not null and not empty, throw an SQLException with SQLState 0A000
>   - if the map is not null and empty, do nothing
> The behaviour on the client driver is this:
>   - always throw an SQLException with SQLState 0A000
> We should try to make the two drivers behave the same way when setTypeMap() is called.
(This would also allow us to simplify some of the tests in J2EEDataSourceTest).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message