EM does actually enter the empty columnName attribute into the dictionary for each attribute, but removing it as EOModeler does (so that it turns out to be null?) did not seem to have an impact (note: I have gone back and tested and confirmed that this does not matter). I tried creating a new test project to verify or reproduce that the problem was related to the use of prototypes, or a bad column definition, or to switching from OB to MySQL, but the test project behaved perfectly, and I can't tell what the differences are between that and the project that's actually having the problem. In any case... I don't use enough of them myself for it to be worth the time solving the problem right now, so I'll be leaving it on the backburner, and will implement those fields in the biz logic instead. I certainly seem to be running in to more than my share of weird problems lately... it's getting frustrating! Thanks both of you for the tips, Clark On 29 Oct 06, at 8:09 AM, Mike Schrag wrote: Yeah I don't personally use and derived columns, so I've never seen them in Entity Modeler vs EOModeler. It's possible EM is generating something wrong. If you feel like doing some testing for me, you can make a simple EOModel with a derived column with EOModeler then again with EntityModeler and compare the two attributes in the entity .plist file and see if they are substantively different. |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
