[DERBY-1331] Derby's "set schema" behavior is not compliant with SQL 2003 Foundation spec.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1
• Fix Version/s: 10.5.1.1
• Component/s: SQL
• Assignee: Dag H. Wanvik
• Reporter: Mamta A. Satoor
• Created: 18/May/06 13:20
• Updated: 04/May/09 18:22
• Resolved: 02/Apr/08 15:05

Description

As per SQL2003 Foundation spec, Pg 913 Section 18.6 <set schema statement> 3b) "Otherwise, the default unqualified schema name of the current SQL-session is set to V." As per this line, set schema will only impact the current context on current SQL-session's context stack. But, in Derby, set schema is impacting all the contexts in SQL-session's context stack rather than only the current context. An example of this would be
1)make a database connection
2)set schema to 'schema1'
3)call an external procedure using CALL statement and change schema to 'schema2'
4)After the call to external procedure, check current schema

Step 3 causes a new context creation and that context gets destroyed when external procedure finishes. As per SQL2003, step 3 should only change the schema for the cotext in which the procedure is running, and step 4 should see current schema as 'schema1'. This doesn't happen in Derby. Instead, the set schema statement affects all the contexts in the SQL-session's context stack. In the example above, in step 4, Derby shows current schema to be 'schema2'.

Issue Links

• is depended upon by: DERBY-3690 EmbedPooledConnection doesn't reset schema when creating a new logical connection
• is related to: DERBY-3327 SQL roles: Implement authorization stack (and SQL session context to hold it)