SQLiteStudio won't re-read database when DB is on network share

[saper-2]

Hi,

I have sqlite3 db on server with a script. The script insert & updates some rows, and from ssh via sqlite3 command I can select and see those new & changed record (basic select * from ...).

In SQLiteStudio I have the db connected via samba share (e.g.: \\192.168.1.255\var\www\db\thedb.db3 - db file is RW for both: the samba user & the script).

The problem is:
When I run the same query (select * from ...) in SQLiteStudio I do not see those new/changed records ☹️, unless I click "Disconnect" and "Connect" and execute the query again, then I can see those changes made by script.

It seems to be some kind of cache - is there a option to disable this cache in SQLiteStudio? Because constantly clicking Connect-Disconnect is not a solution 😑

[pawelsalawa]

SQLite is not recommended to be used over network. It's a known issue. You will always encounter some kind of problems eventually and it's not SQLiteStudio bug - it's nature of SQLite: https://sqlite.org/useovernet.html

If you need network database, you should go for client-server solution, like PostgreSQL.

[saper-2]

Hi,

Do you think it can be somehow handled by SQLiteStudio ? I'm using SQLiteStudio for development as its supposed to be used 😄
Maybe option to like "re-connect before each command" or flush(???) connection to force sqlite driver to reload/re-read db?

Hmmm... I think I found way around this limitation: I mount share as drive in windows and this seems to fix the problem of caching 🤔

[pawelsalawa]

Until you encounter another issue.

This is something that SQLiteStudio aims to handle by having a micro-proxy on the other side - see #1303 and #5215. It's the only reliable solution. It's planned for 4.1.0.