FROM : Matt Neuburg
DATE : Sat Aug 19 18:47:46 2006
On Fri, 18 Aug 2006 21:55:15 -0600, Greg Stark <<email_removed>> said:
>I learned something unexpected about Core Data and thought I'd share
>it...
>
>As you may know, when graphically creating a data model in Xcode,
>Xcode does a good job of telling you whether an attribute name that
>you want to use is reserved (e.g., if you try to use the attribute
>name "zone", Xcode will let you know you're not allowed to use that
>name). However, there is at least one reserved name that isn't
>flagged as a problem, and that name is "version".
>
>If you happen to name one of your attributes "version", as I
>unfortunately did, you'll have a lot of fun and excitement tracking
>down why your application is crashing -- especially if you're new to
>Cocoa as I am.
>
>What makes things even more confusing is that when you make the above
>mistake, you can save your Core Data-based document as binary or xml
>store (seemingly without problem, I might add), but you can't save it
>as a SQL store (you'll get [NSCFNumber length]: selector not
>recognized errors...).
>
>Anyway, I hope this note helps others avoid this problem.
Reading the archives would also have helped:
<http://www.cocoabuilder.com/archive/message/cocoa/2005/12/23/153092>
But the failure to call out this information arguably constitutes a bug in
the docs. Please file it! m.
--
matt neuburg, phd = <email_removed>, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
DATE : Sat Aug 19 18:47:46 2006
On Fri, 18 Aug 2006 21:55:15 -0600, Greg Stark <<email_removed>> said:
>I learned something unexpected about Core Data and thought I'd share
>it...
>
>As you may know, when graphically creating a data model in Xcode,
>Xcode does a good job of telling you whether an attribute name that
>you want to use is reserved (e.g., if you try to use the attribute
>name "zone", Xcode will let you know you're not allowed to use that
>name). However, there is at least one reserved name that isn't
>flagged as a problem, and that name is "version".
>
>If you happen to name one of your attributes "version", as I
>unfortunately did, you'll have a lot of fun and excitement tracking
>down why your application is crashing -- especially if you're new to
>Cocoa as I am.
>
>What makes things even more confusing is that when you make the above
>mistake, you can save your Core Data-based document as binary or xml
>store (seemingly without problem, I might add), but you can't save it
>as a SQL store (you'll get [NSCFNumber length]: selector not
>recognized errors...).
>
>Anyway, I hope this note helps others avoid this problem.
Reading the archives would also have helped:
<http://www.cocoabuilder.com/archive/message/cocoa/2005/12/23/153092>
But the failure to call out this information arguably constitutes a bug in
the docs. Please file it! m.
--
matt neuburg, phd = <email_removed>, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
| Related mails | Author | Date |
|---|---|---|
| Greg Stark | Aug 19, 05:55 | |
| Matt Neuburg | Aug 19, 18:47 | |
| mmalc crawford | Aug 19, 19:05 | |
| Greg Stark | Aug 19, 21:54 | |
| Michael Ash | Aug 19, 23:12 | |
| Matthew Firlik | Aug 20, 10:12 | |
| Matt Neuburg | Aug 20, 17:59 |






Cocoa mail archive

