You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/04/10 08:28:16 UTC
[jira] [Resolved] (DERBY-6540) Schema-qualified table names could
be mistaken for transition tables
[ https://issues.apache.org/jira/browse/DERBY-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-6540.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.11.0.0
Issue & fix info: (was: Patch Available)
> Schema-qualified table names could be mistaken for transition tables
> --------------------------------------------------------------------
>
> Key: DERBY-6540
> URL: https://issues.apache.org/jira/browse/DERBY-6540
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.11.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.11.0.0
>
> Attachments: d6540-1a.diff
>
>
> ij version 10.11
> ij> connect 'jdbc:derby:memory:db;create=true';
> ij> create table new(x int);
> 0 rows inserted/updated/deleted
> ij> create table t(y int);
> 0 rows inserted/updated/deleted
> ij> create trigger tr1 after insert on t referencing new table as new select x from app.new;
> ERROR 42X04: Column 'X' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE statement then 'X' is not a column in the target table.
> The error message here is wrong. Column X does exist in APP.NEW, so the CREATE TRIGGER statement should have succeeded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)