FROM : Jerry Krinock
DATE : Mon Nov 19 00:06:47 2007
I get these in my Xcode Run Log when using NSURLConnection:
ERROR: __CFURLCache::ExecuteSQLInsert - cache object is too large to
persist to store.
Now, it is true that, in my app, I have set the NSURLCache to size 0
by doing this:
[[NSURLCache sharedURLCache] setDiskCapacity:0] ;
and obviously that is why I'm getting these messages. The reason I
did this is, because of what my app is doing, I don't want any
downloaded data to be cached. Is somebody inside there trying to tell
me that there is a better way to do this now?
Note that the messages only appear in the Xcode Run Log. They seem to
not appear in the "real" log, Console.app Messages (although I'm still
not 100% sure that I've figured out how to find all the messages in
Leopard's extra-fancy "enhanced" Console.app).
Jerry Krinock
DATE : Mon Nov 19 00:06:47 2007
I get these in my Xcode Run Log when using NSURLConnection:
ERROR: __CFURLCache::ExecuteSQLInsert - cache object is too large to
persist to store.
Now, it is true that, in my app, I have set the NSURLCache to size 0
by doing this:
[[NSURLCache sharedURLCache] setDiskCapacity:0] ;
and obviously that is why I'm getting these messages. The reason I
did this is, because of what my app is doing, I don't want any
downloaded data to be cached. Is somebody inside there trying to tell
me that there is a better way to do this now?
Note that the messages only appear in the Xcode Run Log. They seem to
not appear in the "real" log, Console.app Messages (although I'm still
not 100% sure that I've figured out how to find all the messages in
Leopard's extra-fancy "enhanced" Console.app).
Jerry Krinock
| Related mails | Author | Date |
|---|---|---|
| No related mails found. | ||






Cocoa mail archive

