[ http://issues.apache.org/jira/browse/DERBY-362?page=comments#action_12313673 ]
Satheesh Bandaram commented on DERBY-362: ----------------------------------------- I am marking this as an improvement, instead of a bug. Fixing this problem is not trivial and may have related issues. Discussed this with Dan briefly. The summary of the discussion was that fixing this may cause issues with statement cache, for example. A view created as SELECT * FROM SESSION.T1 may need multiple plans in different connections, depending on whether SESSION.T1 is a permanent table or a temporary table for that connection. It was felt the current behavior is best left as is. > Some of the DDL checks to prevent incorrect temporary table use is incorrect. > These may incorrectly stop access to valid permanant tables in SESSION schema. > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-362 > URL: http://issues.apache.org/jira/browse/DERBY-362 > Project: Derby > Type: Bug > Components: SQL > Versions: 10.0.2.1 > Environment: Generic > Reporter: Satheesh Bandaram > > Use of temporary tables in some DDLs is incorrect. For example, it should not > be possible to create a view on a temporary table or create a trigger. But > the current code checks prevent valid uses of permanent tables in SESSION > schema, mistaking them for temporary tables. Need to check all DDL statements > and temporary table usage errors. > ij> create table session.permTable ( i int); > 0 rows inserted/updated/deleted > ij> create view view1 as select * from session.permTable; > ERROR XCL51: The requested function can not reference tables in SESSION > schema. > ij> create trigger trig1 after insert on session.permTable for each row mode > db2 > sql insert into t1 values (1); > ERROR XCL51: The requested function can not reference tables in SESSION > schema. > ij> create index indSession on session.permTable (i); <============ Works > correctly. > 0 rows inserted/updated/deleted -- 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
