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,
Retu
something different from the
NULL value and try again the delete with coredata.
On Wed, Oct 8, 2008 at 1:05 PM, <[EMAIL PROTECTED]>
wrote:
From: Marc Monguio <[EMAIL PROTECTED]>
How can I delete the two tuples (660 and 661) that have Z_OPT equal to
NULL with coredata ?
Any idea w
I have a coredata application that uses sqlite3 for persistence. One
of my users reported that his application was not responsive and
showed the spinning beach ball of death. If I debug the application
using his database it stops after executing this:
// objectId is the object we want to de
below...
On Jun 19, 2008, at 6:13 PM, Jens Alfke wrote:
On 18 Jun '08, at 3:01 AM, Marc Monguio wrote:
The documentation I've found about "Conditional GET" in the web
says I should be sending "If-Modified-Since" and "If-None-Match"
headers with
Some weird things seem to happen with NSURLRequest when used with
NSURLRequestUseProtocolCachePolicy :
1)
The documentation I've found about "Conditional GET" in the web says I
should be sending "If-Modified-Since" and "If-None-Match" headers with
the contents of "Last-Modified" and ETag" h
