Re: CoreData - sqlite - statement is still active
Re: CoreData - sqlite - statement is still active
- Subject: Re: CoreData - sqlite - statement is still active
- From: Terrence Talbot <email@hidden>
- Date: Thu, 6 Oct 2005 16:09:54 -0700
On Oct 6, 2005, at 3:30 PM, Bill Bumgarner wrote:
On Oct 6, 2005, at 12:03 PM, Terrence Talbot wrote:
No, that's the thing: this should be a very straightforward
exercise. Single document, single context, single thread. The only
diddling I've done is a .dump (and now some selects, see below) of
the document on the command-line to make sure the rows for these
objects are there. They are...
Hmmm... I'm still missing something because I don't understand why
it wouldn't work.
- Did you change the model and try to use an existing store
afterwords?
No. The model hasn't changed in about 100 checkins and the document
was created well past that. In fact, I can build a new document that
will exhibit the same behavior.
- is the database integrity still intact? (You can use 'pragma
integrity_check;' in the SQLite3 command line to check it).
Yep.
[ttalbot@g5 Sample Sites]$sqlite3 Karelia\ Sample.svxSite
SQLite version 3.1.3
Enter ".help" for instructions
sqlite> pragma integrity_check;
ok
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden