Disable WAL-mode File Format in sqlite for Android 9

[avarelahn]

Hello, I have a problem with my application in the android pie version.
When executing the select using this.sqlite.create () to my database, I get the error: code: 5
message: "sqlite3_prepare_v2 failure: no such table: products"
Apparently I created the database but not the table, in previous versions my application worked great, but in the Pie version or greater it gives me this problem. I read that Android 9 introduces an activated default functionality called WAL (write-ahead logging) but I don't know how to disable this in my code, someone could help me with this, I would appreciate it.

---

From @brodybits: this is only an issue when the androidDatabaseProvider: 'system' setting is used when opening the database. See below for further discussion with the user community.

[brody4hire]

A minimal reproducible example is needed: https://stackoverflow.com/help/minimal-reproducible-example

In case you need help with this, commercial support is available from: https://xpbrew.consulting/

[AhmadAyyaz1993]

I am getting the same problem. Is there any way?
Here is the reference related to this issue https://stackoverflow.com/a/53917295

[AhmadAyyaz1993]

At the moment I disabled write ahead logging in this method of the plugin
void open(File dbfile) throws Exception { dbFile = dbfile; // for possible bug workaround mydb = SQLiteDatabase.openOrCreateDatabase(dbfile, null); mydb.disableWriteAheadLogging(); }
but I am not sure if it will work. Because google suggests to use it in onConfigure of DatabaseHelper class.

[brody4hire]

This plugin uses a custom build of SQLite unless you specify otherwise when you open the database. The custom build of SQLite has never used WAL mode.

This information is already documented but is evidently not clear enough.

[AhmadAyyaz1993]

So that means we don't need to disable WAL mode specifically anywhere in plugin? if we are using 'databaseprovide: system' ?

[julientype]

databaseprovide: system <=== creates a persistent journal database running 2 files or whatever FLAVOR THE os IS RUINING..... WAL

The use of persistent journal mode provides a noticeable performance improvement on many systems. Of course, the drawback is that the journal files remain on the disk, using disk space and cluttering directories, long after the transaction commits. The only safe way to delete a persistent journal file is to commit a transaction with journaling mode set to DELETE:

PRAGMA journal_mode=DELETE;
BEGIN EXCLUSIVE;
COMMIT;
Beware of deleting persistent journal files by any other means since the journal file might be hot, in which case deleting it will corrupt the corresponding database file.

Basically your not running an OS data system where you need a persistent journal like FOR reboot android THE persistent journal IS CORRUPTED

an android app is just a single user..........