[Tracker] Large sparql query results

Hi all,

I have a question about large query results from tracker-store. in my experience with SQL databases and their 
client api, when a query results are generated, only a subset are initially transferred to the client. The 
rest are loaded on demand as the client iterates over the results. 

How does libtracker-client handle this? What if the result set is too big to fit in the client memory? Is 
there any sort of incremental result returning ability or callback support with partial results? t


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]