SQLite Database β Gotchas & Best Practices
For full service implementation, constants, data model templates, and common patterns, see references/sqlite-database-api.md.
β οΈ Wrong Package Trap
<!-- β WRONG β these are different libraries with incompatible APIs -->
<PackageReference Include="Microsoft.Data.Sqlite" />
<PackageReference Include="sqlite-net" />
<PackageReference Include="SQLitePCL.raw" />
<!-- β
CORRECT β sqlite-net-pcl by praeclarum + its bundle -->
<PackageReference Include="sqlite-net-pcl" Version="1.9.*" />
<PackageReference Include="SQLitePCLRaw.bundle_green" Version="2.1.*" />Common Mistakes
β Using Environment.GetFolderPath for Database Path
// β Not cross-platform safe β fails on some MAUI targets
var path = Path.Combine(Environment.GetFolderPath(
Environment.SpecialFolder.LocalApplicationData), "app.db3");
// β
Use FileSystem.AppDataDirectory for all MAUI platforms
var path = Path.Combine(FileSystem.AppDataDirectory, "app.db3");β Multiple SQLiteAsyncConnection Instances
SQLiteAsyncConnection is not thread-safe for multiple instances pointing at the same file. Use a single instance via DI singleton:
// β Creating new connections per request
public async Task<List<Item>> GetItems()
{
var db = new SQLiteAsyncConnection(Constants.DatabasePath);
return await db.Table<Item>().ToListAsync();
}
// β
Lazy singleton β one connection, created once
private SQLiteAsyncConnection? _database;
private async Task<SQLiteAsyncConnection> GetDatabaseAsync()
{
if (_database is not null) return _database;
_database = new SQLiteAsyncConnection(Constants.DatabasePath, Constants.Flags);
await _database.ExecuteAsync("PRAGMA journal_mode=WAL;");
await _database.CreateTableAsync<TodoItem>();
return _database;
}β Forgetting WAL Mode
Without WAL, readers block writers. Always enable it at initialization:
await _database.ExecuteAsync("PRAGMA journal_mode=WAL;");β File Operations on Open Database
// β Moving/deleting while connection is open β data corruption
File.Delete(Constants.DatabasePath);
// β
Always close first
await databaseService.CloseConnectionAsync();
if (File.Exists(Constants.DatabasePath))
File.Delete(Constants.DatabasePath);Platform Pitfalls
| Platform | Pitfall |
|---|---|
| iOS | FileSystem.AppDataDirectory is iCloud-backed β use FileSystem.CacheDirectory to exclude DB from iCloud backup |
| All | Multiple SQLiteAsyncConnection instances to same file β data corruption |
| All | No WAL β readers block writers, poor concurrent performance |
| All | File operations on open DB β corruption |
Decision Framework
| Question | Recommendation |
|---|---|
| DI lifetime? | Singleton β one connection, WAL handles concurrent reads |
| WAL mode? | Always enable β no reason not to on mobile |
| Database path? | FileSystem.AppDataDirectory β never Environment.GetFolderPath |
| Save pattern? | Check Id != 0 β Update, else Insert |
| Multiple tables? | Add all CreateTableAsync<T>() calls in lazy init |
| Need to export/backup? | Close connection first, then File.Copy |
Performance Tips
- Use transactions for batch writes β individual inserts are slow; wrap in
RunInTransactionAsync - Add
[Indexed]to frequently queried columns β especially foreign keys - WAL mode eliminates reader/writer contention
- Avoid
ToListAsync()on large tables β useWhere()filtering and pagination - Use raw SQL for complex queries β
QueryAsync<T>is faster than chained LINQ for joins
Checklist
- Install
sqlite-net-pcl+SQLitePCLRaw.bundle_green(notMicrosoft.Data.Sqlite) - Database path uses
FileSystem.AppDataDirectory - Models have
[PrimaryKey, AutoIncrement] - Single
DatabaseServicewith lazy async init pattern - WAL enabled via
PRAGMA journal_mode=WAL -
DatabaseServiceregistered as singleton in DI - Connection closed before any file move/copy/delete
- iOS: DB excluded from iCloud backup if needed