Can you give any hints about how you wrapped the PK Gen? The easiest way I see is to let MySQL generate the keys itself. How could I go about that? Ie, create table myTable (id int not null auto_increment, other cols) and then turn off EOF PK generation. Does that seem like a good alternative, but then EO would not know what the PK is.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anjo Krank Sent: Thursday, May 18, 2006 3:03 PM To: Robert Walker Cc: Development WebObjects Subject: Re: PK Generation in MySQL Am 18.05.2006 um 20:24 schrieb Robert Walker: > Generally PK generation is a function EOF not MySQL. There are > plug-ins that support database native PK generation, as is the case > with "OpenBasePKPlugIn." but I'm not aware of anything similar for > MySQL. > > In any case, unless you're using something special, this problem > likely has nothing to do with MySQL. The problem would exist no > matter what data store is used. The problem is most likely because the default EOF pk generation doesn't use the table type for mysql that support transactions. Way back when I was using mysql, I was overriding the PK gen by wrapping it with "LOCK TABLES;"..."UNLOCK TABLES;" or sth like it. Cheers, Anjo _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/cawineguy%40gmail.com This email sent to [EMAIL PROTECTED] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
