[DERBY-3853] Behaviour of setTypeMap() differs between embedded and client

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.5.1.1
• Fix Version/s: 10.6.1.0
• Component/s: JDBC
• Issue & fix info: Newcomer
• Bug behavior facts: Embedded/Client difference
• Assignee: Yun Lee
• Reporter: Knut Anders Hatlen
• Created: 26/Aug/08 14:20
• Updated: 30/Jun/09 16:06
• Resolved: 11/Apr/09 17:07

Description

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).

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.