[DERBY-3690] EmbedPooledConnection doesn't reset schema when creating a new logical connection

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.1.1.0, 10.2.1.6, 10.3.1.4, 10.4.1.3
• Fix Version/s: 10.4.2.0, 10.5.1.1
• Component/s: JDBC
• Assignee: Kristian Waagan
• Reporter: Knut Anders Hatlen
• Created: 23/May/08 11:17
• Updated: 04/May/09 18:22
• Resolved: 03/Jun/08 12:46

Description

If you set the schema on a logical connection obtained from EmbedPooledConnection, that schema will also be the current schema for subsequent logical connections obtained from the same EmbedPooledConnection.

Issue Links

• depends upon: DERBY-1331 Derby's "set schema" behavior is not compliant with SQL 2003 Foundation spec.
• depends upon: DERBY-3327 SQL roles: Implement authorization stack (and SQL session context to hold it)
• relates to: DERBY-3859 Reset the current role when EmbedPooledConnection creates a new logical connection
• relates to: DERBY-3692 'javax.transaction.xa.XAException' ++ in 'J2EEDataSourceTest'