I thought SQLite created a journal file, regardless… since it doesn’t “know” that you are not going to write to it
and that that journal file was created (ie. IT is written) at the same location as the database
SQLite only creates additional files when WAL is activated, but I think this is not the case. Is the same when SQLite is used on iOS sandboxed apps: no WAL (multiuser) access possible.
Dave is correct, connecting to SQLite with Xojo creates the extra files whether you like it or not. I have had an app rejected from the MAS because I forgot about this. It’s not hard to work around. Copy the sqlite database out of the app to either app support or temporary to open it.
From what I’ve read of the Sqlite docs, I was under the impression that it only created the extra file if you used WAL… but of course Xojo inc could change that in its plugin which is why I asked…
If the plugin’s behavior in that respect is different from that of SQLite itself, that should be documented in the language reference,
In any case if it’s not needed by SQLite, Xojo’s plugin should avoid doing it if possible.
BTW for DB’s I’m going to write to (most cases), I do as you suggest… But I did not see the point of doing that for a read-only DB, as it is conceptually no different form any other resource
Little things like that make do make a difference in the Xojo experience… but even Apple no longer pays attention to the little things that make a better experience!