When we had this situation, we ended up making external apps do it the
EO_PK_TABLE way. We logged the SQL to see exactly the statements EOF
used to generate PKs and created a subroutine in the non-WebObjects
app that used the same SQL pattern as EOF to get a PK from the
EO_PK_TABLE. I forge
On Oct 4, 2008, at 4:58 AM, Q wrote:
The reason that WO just doesn't work well with AUTO_INC is because
it expects to be able to obtain an id for the EO BEFORE the insert
is executed so that it can resolve temporary id's and any foreign
keys in a transaction safe way. When you use AUTO_INC
Hi Quinton,
Thank you very much for this explanation, it makes a lot more sense
now.
But I'm not completely dissuaded by this. The next AUTO_INCREMENT
key is stored in table metadata - where it can be read and written
to. So would it not be possible to hack the mysql driver to use
Hi Quinton,Thank you very much for this explanation, it makes a lot more sense now.But I'm not completely dissuaded by this. The next AUTO_INCREMENT key is stored in table metadata - where it can be read and written to. So would it not be possible to hack the mysql driver to use this value inste
On 04/10/2008, at 5:31 PM, Richard Stephens wrote:
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 t
if you have to get WO to work with an auto increment column then i
wouldn't have thought changing DB is going to help you much ?
i wouldn't recommend tinkering with how WO does it's PK stuff. it's
more than likely going to be less pain to change the PHP apps. maybe
look at stored procedures
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. Alter
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
Hi
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.
Regards,
Richard Stephens
Ph: 0
