In my embarrassment at my haste to post to the list I have compounded
the error. :(
For archive posterity, the 'bug' was a case of mistaken identity. As I
have since learned, the 'too large' error notification was triggered
by a value-violation in a bounded, 'Number'-attribute that happened to
have the same name as a relation in in different entity on which I had
been working.
The error did not indicate the entity, only the attribute name, in
which the violation had been detected so I jumped to the conclusion
that the error was in the entity on which I had been working when, in
fact, the application was behaving 'correctly'.
No bug, No foul.
Note to self: Make sure error messages contain sufficient identifying
information!
Frederick Bartram
*-------------------------------------------------
* Stop spam before it gets to your mailbox! Support blocklists.
* I use http://www.spamcop.net/.
* my PGP key id: 0x63fa758 keyserver: http://keyserver1.pgp.com
*/
On Sep 24, 2009, at 5:02 PM, Fritz Anderson wrote:
On 24 Sep 2009, at 3:24 PM, Frederick Bartram wrote:
My bad. I apologize for wasting bandwidth.
Problem had nothing to do with relation set size.
It won't have been a waste of bandwidth if you post the meaning of
the error message, and the solution, for the benefit of the archives.
— F
--
Fritz Anderson -- Xcode 3 Unleashed: Now in its second printing -- <http://x3u.manoverboard.org/
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
