Drift Example

[rkistner]

POC of using Drift as an ORM for the supabase-todolist demo.

The bulk of the integration is in the drift_sqlite_async.dart file, loosely based on the drift_sqflite query executor. The implementation applies to sqlite_async in general - nothing is directly coupled to PowerSync.
Update: Uses the new drift_sqlite_async package.

Tested and working:

• Querying
• Watching queries
• Insert, update and delete
• Custom queries
• Transactions, nested transactions
• Drift migrations (not that relevant when using PowerSync).

[rodydavis]

You can make drift work with concurrency via WAL mode:

Native

...
return NativeDatabase.createInBackground(
     file,
     logStatements: logStatements,
     cachePreparedStatements: true,
     setup: (db) {
       db.execute('PRAGMA journal_mode=WAL');
       db.execute('PRAGMA busy_timeout=100');
     },
);
...

Web (WASM)

...
final result = await WasmDatabase.open(
     databaseName: dbName.replaceAll('.db', ''),
     sqlite3Uri: sqliteUrl,
     driftWorkerUri: Uri.parse('/drift_worker.js'),
     initializeDatabase: preload,
     localSetup: (db) {
       db.execute('PRAGMA journal_mode=WAL');
       db.execute('PRAGMA busy_timeout=100');
     },
);
...

[rkistner]

In this case the database is managed by sqlite_async, which already uses WAL mode. The problem is with write we interact with Drift, we need write locks even for select statements (implicit in db.execute), we prevents any actual concurrency.

Also FWIW, no current VFS supports PRAGMA journal_mode=WAL on web/WASM.

[rkistner]

Now published as drift_sqlite_async v0.1.0-alpha.1:

https://github.com/powersync-ja/drift_sqlite_async
https://pub.dev/packages/drift_sqlite_async

[arbile26]

Is this feature abandoned?
I see it has been 4 months since the first alpha version of drift_sqlite_async is published.
Using Drift with PowerSync is revolutionary! We have many apps can benefit from this feature.
Hope you give more attention to this feature.

[rkistner]

While it may lack some features, we haven't had any significant issue reports for it yet, which is why there hasn't been any updates since.

Right now we're focusing on getting web support stable. Once that is out, we'll work on getting this package better integrated and part of our standard examples.

[rkistner]

Closing in favor of #134.