Owen McKerrow wrote:
Could you please explain that a bit further ? Do you mean I still don't
need the EO_PRIMARY_KEY table ? I just set the primary key in orcale
and in the model and they sort themselves out so its always up to date ?
You dont need EO_PK_TABLE. If you have a table called PERSON
you create a sequence called PERSON_SEQ and thats all there is to it.
As mentioned previously EOModeler can generate the sequences SQL for you
or you can write it (if you need to start at a number higher than 1 for
example).
The only thing is, you need to make sure that your next sequence number
is higher than the largest primary key number for that table/sequence
pair. Otherwise the sequence will return a number that has already been
used for a PK and your DB will throw a primary key contraint violation
exception.
cheers,
- shaun
_______________________________________________
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]
