Hi Romain, thanks for your answers. I didn't knew the Cursor is loaded lazily. But now this is no more mystery for me :) I reduced my table and the Cursor works significantly faster now.
best regards On Dec 15, 7:26 pm, Romain Guy <[email protected]> wrote: > Hi, > > The query doesn't actually do much. TheCursoris lazily loaded so > it's only the first method call to access data (like getCount()) that > loads the content of the rows. > > > On the other hand if I query some ContentProvider (using getContext > > ().getContentResolver().query()) then this query takes about 100 > > milliseconds to finish, which is understood. But then first call (and > > subsequent calls) to any ofCursormethods described above is very > > fast. > > The performance of getContentResolver().query() depends on what the > provider uses as a backend. ACursoris not necessarily backed by a > database. Also, it will depend on how much data you are querying and > returning. > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
