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)" <de...@db.apache.org> on 2006/01/23 20:29:10 UTC
[jira] Updated: (DERBY-702) fk fields order
[ http://issues.apache.org/jira/browse/DERBY-702?page=all ]
Mike Matrigali updated DERBY-702:
---------------------------------
Component: SQL
> fk fields order
> ---------------
>
> Key: DERBY-702
> URL: http://issues.apache.org/jira/browse/DERBY-702
> Project: Derby
> Type: Bug
> Components: SQL
> Reporter: Veaceslav Chicu
>
> create table acc.account
> (
> account_id integer not null,
> plan_id integer not null
> );
> create table acc.trans
> (
> plan_id integer not null,
> credit_id integer not null,
> );
> alter table acc.account add constraint account_pk primary key
> (account_id, plan_id);
> alter table acc.trans add constraint trans_credit_fk foreign key
> (plan_id, credit_id) references acc.account (plan_id, account_id)
> on delete restrict on update restrict;
> SQL Exception: Constraint 'TRANS_CREDIT_FK' is invalid: there is no
> unique or primary key constraint on table 'ACC.ACCOUNT' that matches the
> number and types of the columns in the foreign key.
> if in trans_credit_fk I change with places plan_id, account_id, it works
> it's a probleme of order, but message is wrong
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira