The example code just shows the common case where 32-bit integers are
used for primary keys. If you use long ints as primary keys and have
it modeled as such in your EOModel, then you should just adapt the
code to your case.
King Chung Huang
On Mar 20, 2007, at 12:17 PM, Miguel Arroz wrote:
Hi!
I'm in the state of panic here...
I have modeled my DB using 8 byte primary key values. Apparently
PostgreSQL takes this fine.
I started suspecting that it would not work, because it checks
for an Integer, and the key should be a Long value. The problem is
that... it worked!
What does this mean? WO only supports 4 byte primary keys? That's
not good at all... please tell me I'm going crazy for no reason and
there's something tremendously obvious that I have missed.
Yours
Miguel Arroz
"We have no sympathy for the lost souls
We've chosen the path of disgrace
We give this life to our children
And teach them to hate this place" -- Apocalyptica, Life Burns!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kinghuang%
40mac.com
