[jira] [Resolved] (DERBY-6664) Schema 'null' does not exist when trigger inserts into table with deferred foreign key

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen resolved DERBY-6664.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.11.0.0

I've committed the fix to trunk, revision 1610836.

> Schema 'null' does not exist when trigger inserts into table with deferred foreign key
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-6664
>                 URL: https://issues.apache.org/jira/browse/DERBY-6664
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>              Labels: derby_backport_reject_10_10
>             Fix For: 10.11.0.0
>
>         Attachments: d6664-1a.diff
>
>
> If you modify the repro attached to DERBY-6663 so that the foreign key constraint TREF is INITIALLY DEFERRED, the final insert statement will fail like this:
> {noformat}
> ij> insert into othertable values 1;
> ERROR 42Y07: Schema 'null' does not exist
> {noformat}
> I think the fix will be similar to DERBY-6663. FKInfo needs to store its schemaName field.



--
This message was sent by Atlassian JIRA
(v6.2#6252)