Well, found it in (duh!) the SQLiteDatabase spec: public void setLockingEnabled (boolean lockingEnabled) Since: API Level 1
Control whether or not the SQLiteDatabase is made thread-safe by using locks around critical sections. This is pretty expensive, so if you know that your DB will only be used by a single thread then you should set this to false. The default is true. Parameters lockingEnabled set to true to enable locks, false otherwise On Sep 27, 3:28 pm, DanH <[email protected]> wrote: > First off, no lectures -- I know you're supposed to use a provider for > DB access, but I'm looking at a bug in an existing application -- > > SQLite can be built with or without support for concurrent (multi- > thread/multi-process) access. Does anyone know if the Android version > has concurrency turned on or off? -- 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
