db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6540) Schema-qualified table names could be mistaken for transition tables
Date Tue, 14 Oct 2014 21:52:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171592#comment-14171592
] 

Myrna van Lunteren commented on DERBY-6540:
-------------------------------------------

With 10.10, the repro script gives a different warning:
ij version 10.10
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 42X01: Syntax error: Encountered "." at line 1, column 26.
Issue the 'help' command for general information on IJ command syntax.
Any unrecognized commands are treated as potential SQL commands and executed directly.
Consult your DBMS server reference documentation for details of the SQL syntax supported by
your server.

This error remains even after backporting the fix for DERBY-6540, in other words, there is
another bug, or lack of functionality, so DERBY-6540 doesn't even exhibit.
Note by the way that the number in the Syntax error is apparently starting with the 'as' clause.
I'll mark this as backport reject for 10.10.

> 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.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>              Labels: derby_backport_reject_10_10
>             Fix For: 10.11.1.1
>
>         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.3.4#6332)

Mime
View raw message