2008/8/13 Gustavo Vera <[EMAIL PROTECTED]>: > Maybe I should not, but I'm doing it anyway :D > I'm looking inside and also I'm manipulating the structure and data of the > sqlite file since about 200 revisions in my project. I'm doing this to > provide newer versions of the app that has the possibility of performing > database migrations / upgrades from older versions of the app if available. > With the new functionalities, occasionally a change in the database > structure results necessary, and when the change is simple (for example, > just adding a new attribute to an entity) altering the data model and the > data structures in an old sqlite is far easier and faster than implementing > the migration functionality suggested in the documentation. In fact, I think > this is faster and easier even when more complex changes are necessary. > Anyway... I was wondering if I should take care of the Z_UUID during the > perform of this upgrades, or if I can just ignore it. I'm currently ignoring > it... can this become a problem in the future?
Well, I'm not a Core Data expert, but locking yourself to sqlite engine does not look correct to me. Apple can add/remove/change persistent stores anytime. And remember, Core Data is a object graph management framework, not a database. :: marcelo.alves _______________________________________________ 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 [EMAIL PROTECTED]
