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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2014/09/25 01:16:34 UTC
[jira] [Updated] (DERBY-6668) Truncating a table may silently
violate a deferred foreign key.
[ https://issues.apache.org/jira/browse/DERBY-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-6668:
----------------------------------
Labels: derby_backport_reject_10_10 (was: backport_reject_10_10)
> Truncating a table may silently violate a deferred foreign key.
> ---------------------------------------------------------------
>
> Key: DERBY-6668
> URL: https://issues.apache.org/jira/browse/DERBY-6668
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.11.1.1
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Labels: derby_backport_reject_10_10
> Fix For: 10.11.1.1
>
> Attachments: derby-6668-01-aa-disallowTruncateOnReferencedTable.diff, derby-6668-01-ab-disallowTruncateOnReferencedTable.diff
>
>
> If you truncate a table which is referenced by a deferred foreign key, orphaned tuples are left in the foreign table. That is, the foreign key is violated but no exception is raised.
> Since table truncation involves changing conglomerate ids, this may be another case of derby-6665. Or this may be a new bug.
> The following script shows this behavior:
> {noformat}
> connect 'jdbc:derby:memory:db;create=true';
> create table tunique
> (
> a int not null unique
> );
> create table tref
> (
> a int references tunique( a ) initially deferred
> );
> insert into tunique values ( 1 );
> insert into tref values ( 1 );
> truncate table tunique;
> -- the unique table is empty
> select * from tunique;
> -- but the table which references it has a row
> select * from tref;
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)