[jira] Resolved: (DERBY-405) SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables
[ http://issues.apache.org/jira/browse/DERBY-405?page=all ] Kathey Marsden resolved DERBY-405: -- Fix Version: 10.1.3.0 10.1.2.4 10.1.1.0 Resolution: Fixed Assign To: Satheesh Bandaram Fixed in 10.1 with revision 208776 - In preparation for the 10.1 release, roll up fixes from trunk. SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables --- Key: DERBY-405 URL: http://issues.apache.org/jira/browse/DERBY-405 Project: Derby Type: Bug Components: SQL Versions: 10.2.0.0 Reporter: Mamta A. Satoor Assignee: Satheesh Bandaram Fix For: 10.1.3.0, 10.2.0.0, 10.1.2.4, 10.1.1.0 A user should not be able to create a synonym in SESSION schema eg create synonym session.st1 for app.t1; select * from session.st1; -- refers to app.t1 declare global temporary table st1(c11 int, c12 int) on commit preserve rows not logged; select * from session.st1; -- refers to app.t1, is that right? I think the last select * from session.st1 should goto temporary table st1 since any references to objects in SESSION schema should first find a match against a temporary table if one by that name exists. We already discourage users from defining objects other than temporary table in SESSION schema in the reference manual Using SESSION as the schema name of a physical table will not cause an error, but is discouraged. The SESSION schema name should be reserved for the temporary table schema. But, IMHO, it will be nice to enforce this wherever possible in Derby code rather than leaving it upto the users to avoid confusion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-405) SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables
[ http://issues.apache.org/jira/browse/DERBY-405?page=all ] Satheesh Bandaram resolved DERBY-405: - Resolution: Fixed Fix has been merged into trunk. This may get ported to 10.1, if Andrew, the release czar, decides this is important for 10.1 release. SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables --- Key: DERBY-405 URL: http://issues.apache.org/jira/browse/DERBY-405 Project: Derby Type: Bug Components: SQL Versions: 10.2.0.0 Reporter: Mamta A. Satoor Fix For: 10.2.0.0 A user should not be able to create a synonym in SESSION schema eg create synonym session.st1 for app.t1; select * from session.st1; -- refers to app.t1 declare global temporary table st1(c11 int, c12 int) on commit preserve rows not logged; select * from session.st1; -- refers to app.t1, is that right? I think the last select * from session.st1 should goto temporary table st1 since any references to objects in SESSION schema should first find a match against a temporary table if one by that name exists. We already discourage users from defining objects other than temporary table in SESSION schema in the reference manual Using SESSION as the schema name of a physical table will not cause an error, but is discouraged. The SESSION schema name should be reserved for the temporary table schema. But, IMHO, it will be nice to enforce this wherever possible in Derby code rather than leaving it upto the users to avoid confusion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
