Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sqlite Caching results #9

Open
jasonbronson opened this issue Jun 11, 2021 · 4 comments
Open

Sqlite Caching results #9

jasonbronson opened this issue Jun 11, 2021 · 4 comments

Comments

@jasonbronson
Copy link

  1. Which driver are you using and version of it (Ex: PostgreSQL 10.0):
    Sqlite

  2. Which TablePlus version number are you using:
    Build 274

  3. 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.

@huyphams
Copy link
Contributor

huyphams commented Jun 11, 2021

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.

@jasonbronson
Copy link
Author

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?

@huyphams
Copy link
Contributor

huyphams commented Jun 11, 2021

Thank you, we are aware of it. Mounting file from host to local is not easy. We are working on it for a while

@jasonbronson
Copy link
Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants