On Oct 8, 2009, at 8:28 PM, David Melgar wrote:
I read a little on ICU and now understand that sqlite by default
does not handle case insensitive unicode.
Is there an easy way to make sqlite use ICU on the Mac, or do I have
to build it myself with ICU enabled?
Probably the easiest thing to
I read a little on ICU and now understand that sqlite by default does
not handle case insensitive unicode.
Is there an easy way to make sqlite use ICU on the Mac, or do I have
to build it myself with ICU enabled?
Based on the derived property example, it seems that I would need to
duplicate
On Oct 7, 2009, at 10:12 PM, David Melgar wrote:
Hello,
I didn't mean to state threads as a requirement when I said "async",
I just meant some way to get partial results, such as a call to a
delegate I referenced in the previous note. And I'm certainly not
seeking complexity of threads if
On Oct 6, 2009, at 8:29 PM, David Melgar wrote:
Hello,
Thanks for the response. Seems that its straying somewhat from my
original question.
Sure, your original question is that you have a serious performance
issue, and you'd like to hide it from the user by adding threads. I'm
proposin
On Oct 6, 2009, at 1:08 AM, Ben Trumbull wrote:
Core Data is just passing the query off to the database. I'm not
sure why you think going to the database directly will do anything
for the 179.9 / 180.0 seconds it takes to evaluate the query in the
database.
I suspect that he wants a back
Hello,
Thanks for the response. Seems that its straying somewhat from my
original question.
Searching based on prefix matching is fine. The predicate I'm using
really is of the form "SELF like foo", no wildcard, so it doesn't seem
that it should be that expensive. You say its possible to
On Oct 5, 2009, at 7:00 PM, enki1...@gmail.com wrote:
I am doing a simple query search for a text string pattern (ie 'SELF
like foo') on ~10 million small records stored persistently using
sqlite. This is a performance test to make sure I get reasonable
performance from my database engine
I am doing a simple query search for a text string pattern (ie 'SELF like
foo') on ~10 million small records stored persistently using sqlite. This
is a performance test to make sure I get reasonable performance from my
database engine before I commit too much code to it.
The query is takin
Is there a way to do an asynchronous fetch request against Core data
returning partial results?
That depends on whether it's the query part that's expensive (e.g.
WHERE clause with complex text searching and table scans) or simply
the quantity of the row data that's your problem. For the la
Is there a way to do an asynchronous fetch request against Core data
returning partial results?
Try spawning the fetch in a background thread. There is an example of
this in the CoreData sample project 'BackgroundFetching'. You will
need to read up on the threading issues as in "don't share co
I'm fairly new to Core Data but I do believe that when tieing an
NSFetchedResultsController with an NSManagedObjectContext and an
NSTableViewController, (yes, this is an iPhone example) indeed, results for
the NSTableView are retrieved lazily, ie: as necessary.
I do not know how this is implemente
11 matches
Mail list logo
