Re: OpenBase and Cannot update primary-key 'fooID' from '1364' to '1364' on object of entity Foo
Re: OpenBase and Cannot update primary-key 'fooID' from '1364' to '1364' on object of entity Foo
- Subject: Re: OpenBase and Cannot update primary-key 'fooID' from '1364' to '1364' on object of entity Foo
- From: Chuck Hill <email@hidden>
- Date: Tue, 24 Mar 2009 17:28:48 -0700
On Mar 24, 2009, at 5:19 PM, Ricardo J. Parada wrote:
Hi All,
I searched Google first for similar problems and I found some but I
could not figure out what the resolution was. These were old
messages (2004 or 2006 I think). But anyways, I think I have a clue.
EOF thinks that the primary key value has changed but it hasn't. So
my guess is that the value in the snapshot of the EO and the value
in the EO are not matching... not completely sure why.
I have the primary key fooID turned on as a class property in my Foo
entity. I'm thinking that may have something to do. Maybe if I
turn it off will make it go away.
Exposing the PK, while generally considered naughty, will not cause
this. Exposing a FK _will_.
fooID in OpenBase is a foo_id of type long. In my eomodel I used
the "id" prototype from ERPrototype. Which it says the external
type is an int. But like I said, in OpenBase it is really a long.
Could this long in OpenBase vs. int in my eomodel cause a problem
like this?
Has anybody ran into this problem with OpenBase?
I think Mike is on this. Usually it is a Long vs Integer problem
where the value is the same, but the class is not.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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