Hi Michael,
The 'could not open field slot' error might be due to a single query returning more than 1MB of data, this is a known issue and has been fixed. The fix will be released with the next release of the SDK. SQLiteDatabase does full database level locking, so there shouldn't be any problems with concurrent access going on. The background service queries should be run on a seperate thread to avoid blocking the UI. The AsyncQueryHandler class can be used for constructing non-blocking queries without writing the threading code yourself. Thanks, Megha On Mon, Apr 7, 2008 at 10:48 AM, michael <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a (remote) service that once a while enters data in a SQLite > database. While this service is running, a user might want to query > data from the same database (and table) from an activity. Could this > cause any problems? I once got a "could not open field slot" > exception, which I cannot really reproduce. I thus thought it might be > due to this concurrent DB access... Is this possible? If so, how could > I avoid such problems? Or should I try to search the problem somewhere > else? > > Thanks, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
