Re: mysql AUTO_INCREMENT
Re: mysql AUTO_INCREMENT
- Subject: Re: mysql AUTO_INCREMENT
- From: Richard Stephens <email@hidden>
- Date: Sat, 4 Oct 2008 17:31:01 +1000
| Unfortunately, most of the PHP stuff doesn't use any database abstraction. Converting it to se a different database would be a huge task.
I guess I just don't understand why WO has to store the next key in a table, rather than in the table metadata where AUTO_INCREMENT stores it. Alternatively, in my case, even using SELECT MAX(pk) might be an option, as the WO code doesn't actually create new entities very often.
Is there source available for the mysql driver? I wouldn't mind having a look see if I can adapt it
Regards, Richard Stephens Ph: 07 3136 3426 Mob: 0410 111 570
On 04/10/2008, at 4:10 PM, Guido Neitzer wrote: On 03.10.2008, at 23:32, Richard Stephens wrote: Is there any way to get round having to use EO_PK_TABLE for mysql and to allow WO to use auto_increment instead? I'm writing a WO app that has to share a mysql database with a number of PHP apps, so the data that ends up in EO_PK_TABLE can't be trusted.
We had a hard time doing that (working around issues in MySQL) and ended up converting the projects to either FrontBase or PostgreSQL and within a day all pain was gone ... The problem is, that WO just doesn't work the way, auto-increment works. And it's less pain to use another database than to deal with all these problems in my opinion. If that is not an option, just ignore me ... cug
|
_______________________________________________
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