That looks bad, and it looks like you have enough information to be
worth filing a bug.
I just filed it. Bug ID# 6280722
What version of OSX are you on ?
10.5.5, tried on PPC and Intel with same results.
Two other things you can do are
(a) run "pragma integrity_check" on the db file,
Returns "ok", so there's the database itself is not corrupt, it's just
coredata who left in an unstable mode for him to work afterwards
(b) "delete from zplayedtrack where z_pk in (660, 661)"
Yes, that works, the next tuples do work with CoreData as expected.
Unfortunately this is not a solution since I should not be accessing
sqlite db directly.
_______________________________________________
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]
