Repository navigation
Sqlite Caching results #9
Description
Activity
HI @jasonbronson TablePlus will copy the SQLite from the server to local every time you connect over SSH. So it is not cached, but it clones a new connection every time.
This is the limitation (known issue), we're still finding a way to mount the file from the server to local so we can update it.This would cause major issues assuming working with very large Sqlite databases especially over a very low internet connection. Imagine a very large instance of 4GB Sqlite db. Now you are copying that from a mobile internet connection every time.
Couldn’t you make a db connection directly to the source over ssh opening and closing on every call?Thank you, we are aware of it. Mounting file from host to local is not easy. We are working on it for a while
@huyphams are you able to at least after a commit is run to write it back? My current problem is non of the data you change is written back to the original file.
Which driver are you using and version of it (Ex: PostgreSQL 10.0):
Sqlite
Which TablePlus version number are you using:
Build 274
The steps to reproduce this issue:
create Sqlite over ssh with simple table
insert some data from another source outside of tableplus
run the query “select * from table”
results come back
run the query “delete from table”
results are now empty
close connection
open connection again
run the query “select * from table”
all results still found
Expected 0 rows since no other source inserted after delete
It’s like tableplus is caching the data because i can delete from another source and table plus retains all rows still.