Re: MySQL and Foreign Keys
Re: MySQL and Foreign Keys
- Subject: Re: MySQL and Foreign Keys
- From: Kieran Kelleher <email@hidden>
- Date: Fri, 25 Mar 2005 13:11:24 -0500
This seems to be a common problem that is easily solved if you allow
WebObjects manage foreign key constraints and not the DB. In other
words, use the Mandatory/Optional settings in EOModeler's relationship
inspector and do not use foreign key constraints in the database. Using
foreign key constraints in the DB can make it impossible to implement
some types of inheritance also.
Regards, Kieran
On Mar 23, 2005, at 11:01 AM, Doug Andrews wrote:
Is there a way to get EOF to order database operations when using MySQL?
Basically, here is the problem:
Table A has a 'to one' relationship with table B.
I want to add a record to both tables within the same transaction, but
if i cannot control the order of database operations, i will get a
foreign key constraint error.
FrontBase has the "DEFERRABLE INITIALLY DEFERRED" option for your
foreign keys that would solve this problem.
There does not seem to be an option like this for MySQL.
Does anyone know how to deal with this issue when using MySQL?
- Doug Andrews
- Baseview Products
- Ann Arbor, MI
- email@hidden
_______________________________________________
WebObjects-dev mailing list
email@hidden
http://www.omnigroup.com/mailman/listinfo/webobjects-dev
_______________________________________________
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