Re: Why doesn't EOF sort our PK problems itself ?
Re: Why doesn't EOF sort our PK problems itself ?
- Subject: Re: Why doesn't EOF sort our PK problems itself ?
- From: Mike Schrag <email@hidden>
- Date: Wed, 23 Jan 2008 17:43:29 -0500
Not really related to this but... I remember some years back
asserting on the list that it was impossible for EOF work with auto-
increment columns. Someone proved me wrong but I don't recall who
or what the solution was. It was pretty low level IIRC. Insert
cursors or some such so that EOF could get the PK after insert and
use it for the global ID.
... Wait, yeah, actually for the exact reasons we were talking about,
that the pk doesn't commit inside of EOF until after the commit of the
DB. You'd have to combine it with your ordering stuff for MS SQL +
your decree of no cyclic dependencies and probably wrap JDBCChannel so
you can catch the performAdaptorOperations and grab the last insert
value out of the JDBC connection then muck with the database
operations to switch around its PK after the insert. It would be
horrible and ugly, but I bet it would work ...... or you could just
switch to postgresql :)
ms
_______________________________________________
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