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 17:19:15 -0500
They are models that I routinely edit, My last edit was about 1 week
ago and it worked without problems. What triggered those explicit
className field to appear ?
As I said earlier. I updated Wonder last night and I assume the
stricter checking is recent.
Yes, Wonder explicitly checks for these now, because they can cause
really strange problems ... When did you last update wolips? Are you
on nightly? Is it possible to compare this to your version control
and see how long they've been there? There was one version of Entity
Modeler that would accidentally introduce these (when I was trying to
fix some other bug related to classNames) and the next update (I
thought) fixed it. It's possible I'm still somehow generating these
values.
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