db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6357) CREATE TRIGGER doesn't detect all illegal references to SESSION schema
Date Mon, 30 Sep 2013 14:38:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-6357:
--------------------------------------

    Issue & fix info: Patch Available,Repro attached  (was: Repro attached)

> CREATE TRIGGER doesn't detect all illegal references to SESSION schema
> ----------------------------------------------------------------------
>
>                 Key: DERBY-6357
>                 URL: https://issues.apache.org/jira/browse/DERBY-6357
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.10.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: d6357-1a.diff
>
>
> The reference manual's section on the DECLARE GLOBAL TEMPORARY TABLE statement says:
Temporary tables cannot be referenced in a triggered-SQL-statement
> It detects most cases and reports:
> ERROR XCL51: The requested function can not reference tables in SESSION schema.
> However, some references are not detected if they are in a subquery. For example:
> ij version 10.10
> ij> connect 'jdbc:derby:memory:db;create=true';
> ij> declare global temporary table temptable(x int) not logged;
> 0 rows inserted/updated/deleted
> ij> create table t1(x int);
> 0 rows inserted/updated/deleted
> ij> create table t2(b boolean);
> 0 rows inserted/updated/deleted
> ij> create trigger tr1 after insert on t1 insert into t2 values exists(select * from
session.temptable);
> 0 rows inserted/updated/deleted
> This CREATE TRIGGER statement should have raised an error.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message