db VS dbeaver

We actually did work on this a few years ago but did not get enough takers for it. We created a one size fits all database, that leverages the full capability of the file system.

Try it here: https://github.com/blobcity/db

PS: I am the chief architect of the DB, and the project is no longer being actively maintained by us. But if you make a contribution, we will oblige to review and merge a PR.

Bottom line, nothing you do can make your database faster than the filesystem. So why not make a database that just uses the filesystem to the fullest, than creating a filesystem on top of a filesystem. BlobCity DB does not create a secondary filesystem. It dumps all data directly to the filesystem, thereby giving peak filesystem performance. This is scientifically really the best it gets from a performance standpoint. Not necessarily the most efficient in data storage / data-compression standpoint.

This means, we gain speed, while compromising on data-compression. We produce a larger storage footprint, but are insanely fast. Storage is cheap, compute isn't. So that should be okay I suppose.

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?