Re: Core data app & data loss
Re: Core data app & data loss
- Subject: Re: Core data app & data loss
- From: Wdyp <email@hidden>
- Date: Fri, 7 Dec 2007 00:14:06 +0100
I don’t know how Apple’s bug fixing process works, but this is a
serious one
and I can’t understand how it is possible not to get it fixed right
now…?
Is it impossible for engineers like the ones at Apple to find the
cause of such a bug?
Couldn’t they simply embed the changes-check trick in the inner save:
method to
prevent modest developers and their users from loosing data???
I noticed this bug only after upgrading stores with the new versioning
system and
thought I might have done something wrong. Fortunately, Time Machine
was there
(as long as it didn’t, like yesterday, just corrupted my external
drive, other frequently
reported bug about Leopard that should really be addressed…).
That was my 5 minutes angry moment of the day.
Flofl.
I have a strange problem with my Core Data app, and not sure what to
do about it. This Core Data app was written several years ago and
has been very stable under Tiger with no reported bugs. However,
when Leopard came out, about 10 people (less than 1% of the amount
of users) told me that after they upgraded to Leopard, they
experienced data loss with my app. I haven' t been able to pinpoint
it down, but it seems to occur after they perform some edits and
then save (or Save As) the file. Later they come back to the file
only to find the file completely empty (file size zero K). The app
only saves file in XML format (not binary or SQLite format).
<http://www.cocoabuilder.com/archive/message/cocoa/2007/11/2/192085>
mmalc
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden