[
https://issues.apache.org/jira/browse/DERBY-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3853:
--------------------------------------
Attachment: releaseNote.html
Here's an attempt on a release note for this issue.
> 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
> Fix For: 10.6.0.0
>
> Attachments: DERBY-3853-1.patch, DERBY-3853-1.stat,
> DERBY-3853-2.patch, DERBY-3853-2.stat, releaseNote.html
>
>
> 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.
