[jira] [Updated] (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 updated DERBY-6664:
--------------------------------------

    Attachment: d6664-1a.diff

The attached patch [^d6664-1a.diff] contains a test case and a fix for the problem. I'll start a run of the regression test suite.

> 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
>         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)