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 09:25:45 -0500
Why does EOF throw an exception ? Why doesn't it just say, "hey,
somethings not write here, i'll do a MAX() and sort myself out" ?
Probably the reason is that it generates the PK first from your
eo_pk_table, then writes the EO to the database much later in the
process. The writing of the EO to the database is the part that fails,
at which point it's already switched out your EO's temp global id for
a real global id. It would be a likely very nasty architectural
change to get that to behave the way you want, because it would have
to essentially change your EO's global ID. Assuming that is the case,
I think you should make the more generally useful request "support
autoincrement pk columns and end this eo_pk_table silliness". It
would ALSO take a substantial architectural change, but it puts you in
a much better position at the end of it.
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