summaryrefslogtreecommitdiff
path: root/tests/DynamicCodeLoggerIntegrationTests/src
diff options
context:
space:
mode:
author Lee Shombert <shombert@google.com> 2025-01-10 08:49:27 -0800
committer Lee Shombert <shombert@google.com> 2025-01-13 10:38:25 -0800
commit80d8343a7335e3fb0aa1c0161b784c921b32b2bb (patch)
tree01ba7cd495be30dcdb09b9811622fa77fe037adf /tests/DynamicCodeLoggerIntegrationTests/src
parente302462c12cd01a3dcfe7dfd9770386861f735fb (diff)
Make SQLiteOpenHelper thread safe
Concurrent SQLiteOpenHelper instances is a common anti-pattern that leads to SQLiteDatabase exceptions. The specific problem occurs when a database upgrade is triggered automatically inside the open helper. This creates a lock for every database file managed by a SQLiteOpenHelper. The lock guards the code that opens a database and optionally upgrades it. This does not protect against code that might access the database outside of a SQLiteOpenHelper. Flag: android.database.sqlite.concurrent_open_helper Bug: 335904370 Test: atest * CtsDatabaseTestCases * FrameworksCoreTests:android.database Change-Id: I4d79375c44ca3170495fce6cd9d682cf21e62e2f
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src')
0 files changed, 0 insertions, 0 deletions