3 ms·

How does this handle permissions over data? I wouldn't want a user accessing private information of another. How would you "hide parts of a table" to a client-s

• IMTDb 3y ago
  All data are local; this allows you to use sql.js in the browser with persistence. Unless the developer adds synchronisation primitive to sync data between multiple clients all data are local.
  • bbor 3y ago
    Synchronization in this space being covered under the term “Local First” Web Applications, if anyone wants to look into it more. Almost all the frameworks I saw in that space have access controls built in - both between clients and for privileged server-only data. I agree with the other commenter though that by putting a DB on the client, you’re implicitly trusting that client more than usual to only make acceptable changes to the DB. If you’re working in a sensitive context, I think Local First means you’ll have to spend some extra time planning out data security
  • dariosalvi78 3y ago
    which is a big limitation given that Safari will destroy all the data after one week of no usage. The idea is great, but these limitations make it basically useless on all iPhones.
• samtho 3y ago
  You really have to shift thinking away from the centralized-database model in order to fully understand why this question seems ill-informed. If you recall from the SQLite story, it was created, in-part, to provide a local cache to an offline device yet still have the same query interface that developers enjoy. Because the model of access is shifted to the device, anything you populate a client-side SQL database with is already data that is accessible by the client.
  • deleted 3y ago
    [deleted]