Re: Derby problem
Re: Derby problem
- Subject: Re: Derby problem
- From: WebObjects - Anazys <email@hidden>
- Date: Wed, 2 Sep 2009 11:31:53 +0200
Thanks for your reply Andrew.
I think I found the problem : to create my database, I copy the code
generated by EOModeler : create table, create primary key AND create
foreign key constraints.
But Derby seems not able to handle foreign key constraints. So I
deleted these foreign constraints from my database and it seems to
work again..
So to summary : DERBY + FOREIGN KEY CONSTRAINT = big problems
Somebody could validate my conclusion ?
So what is the "good" way to create a Derby database ?
Cedric
Le 2 sept. 09 à 02:54, Andrew Lindesay a écrit :
Hello;
Possibly this is because Derby does not support deferred referential
integrity checks.
I think Chuck wrote something which organises the adaptor operations
to try and not violate the constraints from the model, but I don't
know if it is infallible -- cue for Chuck to make a bold claim about
his code being infallible.
cheers.
Next exception:SQL State:23503 -- error code: 20000 -- msg:
INSERT on table 'ENTRY' caused a violation of foreign key
constraint 'ENTRY_USERPORTAL_FK' for key (15). The statement has
been rolled back.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden