dbeaver VS sql.js

Yes but not in the community version:

https://github.com/dbeaver/dbeaver/wiki/Schema-compare

DBeaver is a veteran SQL client. In addition to basic visualization and management capabilities, it has a SQL editor, data and schema migration capabilities, monitor database connections, and more. It supports a full range of databases (both SQL and NoSQL). DBeaver is also hooked up with GPT-3, which converts your natural language to SQL.

If you want to do something meaningful, here's the DBeaver GitHub repo https://github.com/dbeaver/dbeaver. Go contribute a ChatGPT plugin & update the UI to look nicer.

dbeaver is an excellent option as well, plus it supports basically every kind of SQL database in existence.

Curiously enough, just yesterday a snap broke on me. People on the github thread said reverting snap didn't work either - I'm not sure whether they simply couldn't revert, or they reverted and still had issues, as I just saw this and slapped on the flatpak instead of messing with my snap. I'm also not sure whether the snap revert didn't work because of something the dbeaver team screwed up there as well, however I'll make sure to avoid automatic/unattended updates in the future. I'm running Arch on my personal machine anyway, so it's not like I mind running updates regularly, but I'd rather do it at my own discretion.

Please create a ticket and describe your issue here: https://github.com/dbeaver/dbeaver/issues/new/choose

I did find https://github.com/dbeaver/dbeaver/issues/6064 marked as closed, perhaps that will help?

Hi HN! A friend and I were inspired by projects like https://github.com/sql-js/sql.js and the idea of querying files served over CDN with HTTP range requests. We started thinking: what would a database that was specifically designed for this type of use case look like? So we started building one, and we landed on a functional prototype that we're pretty proud of!

With our prototype, Appendable, we're able to serve and query large (GB+) datasets by hosting them on a static file host like Amazon S3 or Cloudflare R2 without running a separate server and worrying about things like tail latency, replication, and connection pooling -- all that is handled for us by the file hoster.

Additionally, one tenet that we have been following is Appendable won't touch your underlying data, so your jsonl file is preserved and we point at that data instead of consuming it into an Appendable-specific file format. This keeps your data yours and makes it easy to introspect the data: just open it up with your favorite editor aka vim.

We're curious what you think, we're excited to build this out further to get the performance even better and add features like pubsub. Everything is open source at https://github.com/kevmo314/appendable.

Kevin and Matthew

My project is powered by sql.js, I recommend checking that out if you're interested - https://github.com/sql-js/sql.js/

Maybe you can try to use some SQL database compiled as Web Assembly Modules? Like this one for example: https://github.com/sql-js/sql.js

If you want to have persistence, then I would go with a database like Dexie, as it uses IndexedDB and has transactions. If you just want something that's in memory, you could look at Sql.js or something simple like lowdb.

not necessarily. you can host an html/js/sqlite site on github pages for free. json -> sqlite3 js -> sql

Link: https://sql.js.org

Does it work with really large files? Like, >100mb or so. I was considering making something similar but with sqlite.js [1], but the problem with it is that it loads everything in memory, so I wasn't entirely sure how it will deal with larger workloads.

[1]: https://sql.js.org/#/