Re: Class names or value type mismach in EOModel ?
Re: Class names or value type mismach in EOModel ?
- Subject: Re: Class names or value type mismach in EOModel ?
- From: Mike Schrag <email@hidden>
- Date: Sat, 17 Jan 2009 16:14:06 -0500
If you look inside the plist, you'll probably find one of them is
explicitly setting the className field of the attribute ... Is one of
these an old model?
On Jan 17, 2009, at 2:52 PM, Louis Demers wrote:
Hi,
since I updated my wonder framework yesterday, I get this message
when my application starts.
java.lang.RuntimeException: The attribute part_id in Bug
(java.lang.Number, i) is a foreign key to id in Part
(java.lang.Integer, i) but their class names or value types do not
match. If this is actually OK, you can set
er.extensions.ERXModelGroup.Bug.part_id.ignoreTypeMismatch=true in
your Properties file.
when I checked the Bug->part_id and Part->id, I do not understand
why they would be declared different. They are both in the same EO-
Model files and I use EOJDBCPostgresqlPrototypes.
<Picture 1.png>
<Picture 2.png>
Louis Demers eng.
www.obzerv.com
_______________________________________________
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
_______________________________________________
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