# Android Sqlite Locking - Kevin Galligan

DevFeed: [Android Sqlite Locking - Kevin Galligan](<https://devfeed.tech/articles/android-sqlite-locking-kevin-galligan-38042.md>)

Original publisher: [Read original article](<https://touchlab.co/2011-01-android-sqlite-locking>)

Published: 2011-01-25T05:00:00Z

Content type: article

Language: en

Sources: [Touchlab | Enterprise Mobile Innovation & Development](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [locking](<https://devfeed.tech/topics/locking.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Database](<https://devfeed.tech/topics/database.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [database](<https://devfeed.tech/tags/database.md>), [locking](<https://devfeed.tech/tags/locking.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [thoughts](<https://devfeed.tech/tags/thoughts.md>)

## AI overview

This article examines SQLite database locking on Android, focusing on SQLiteOpenHelper instances, multiple connections, and concurrent access. It explains that SQLite serializes writes through file-level locking, while simultaneous writes from distinct connections can fail without waiting and may only produce a LogCat message if the wrong SQLiteDatabase method is used.

## Source excerpt

Recently I've been doing quite a bit of work with the Android Sqlite database. Mostly with the android piece of ormlite. The Android examples cover some basic Sqlite usage, but they really don't go into depth with regards to proper usage patters, and more importantly, improper usage patters. Most examples and documentation is slated towards using very basic database queries, and beyond that, creating a ContentProvider.