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?
On Tue, 12 Aug 2008 17:28:39 -0300, Marcelo Alves <[EMAIL PROTECTED]> wrote: > > It is a implementation detail. You should not look inside the sqlite file. > > 2008/8/12 Gustavo Vera <[EMAIL PROTECTED]>: > > What's the use of the Z_UUID in the Z_METADATA table? > > Is some kind of check sum or something like that? > > CoreData uses this value for something? > > Why is this value different every time the DB is regenerated? > > Is the generation of it a random-based one? Or is it based on > > random+"another thing"? > > > > Please don't answer my question with another question!!! At least not at > > first instance! :D > > > > Thanks in advance! > _______________________________________________ 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]
