I'm so fucking sick of the lack of great modern open source DB tooling.

MySQL Workbench can go suck a big fat herpes-ridden cock, it's horrible.

Dbeaver is a clunky 90's tool, which charges two Netflixes (yes, that is a valid $/month monetary unit) just to connect to a NoSQL DB.

Datagrip is nice, but has the same outrageously expensive pricing. I paid for it, and couldn't use it for my local docker DB during my holiday because it couldn't connect to the license server. Fuck you, Jetbrains. Your software is nice, but your DRM makes me hate you.

And then ERD software... It's either some hard-to-use afterthought piece of crap bundled with the DB IDE, some generic diagramming tool which makes DB-specific work needlessly unergonomic, or some vendor-locked online tool.

Fuck this shit, I'm making my own DB admin tool. With blackjack. And hookers. 😡

i nearly had a panic attack when 3 tables contaning transactions shows empty,. then i reconnected dbeaver and it turns out it was fine,. damn my shitty internet!

If you ever decide to make a software, contact the DBeaver developer team and ask them what they did, then do everything exactly the opposite and I'm sure your software will be the most complete, beautiful, bug-free software in the world. Because I am convinced DBeaver is the most incomplete, ugliest
software full of bugs. And also, did these people ever actually use a database administration tool before they decided to make one? It seems like they haven't to me, otherwise it wouldn't be so user-unfriendly.

Note: I am writing this in my calmest, had I written it 30 minutes ago, you would have seen some ugly words.

THEY FORCE ME TO USE PHPMYADMIN THROUGH THEIR INTERFACE. I CAN'T CONNECT WITH DBEAVER. THEY EVEN BLOCK ACCESS THROUGH SSH TUNNEL. WHAT THE ACTUAL FUCK. FUCK YOU ONE.COM. FUCK YOU REAL HARD.

Fuck sequelize, the bloody query generated by the "ORM" give diferent result on the same DB if you trie it on dBeaver (works fine) vs node (shit results).

order DESC have 0 effect on sequelize, but it appears on the logger as part of the query.

I just want to go to sleep ffs.

Interesting...

On Friday, I was playing with the ChatGPT integration in DBeaver. I was using the DBeaver sample SQLite database. This database has a couple of tables, among them Album and Artist, where Album has a foreign key into Artist.

So, I asked it:

"give me a query that lists all albums from artists who's name starts with s"

The query I got back was:

SELECT * FROM Album

Uhh, okay.

But then, I noticed that I wrote "who's" instead of 'whose', which would be proper grammatically. So, I changed that, and then I got this query:

SELECT * FROM Album WHERE ArtistId IN (SELECT ArtistId FROM Artist WHERE Name LIKE 'S%');

Hooray, that works! I'm not sure it's the best way to write the query... I might have written:

SELECT * FROM album a, artist r WHERE a.artistid=r.artistid AND r.name LIKE 'S%'

...I'd have to check to see if one performs better than the other, and consider which syntax I find clearer, but that's a separate issue, it's just nice to see a working, reasonable query generated because that's the point, after all.

But I found it interesting that such a minor error would cause it to not work, that's my main point.

Interestingly, it seems to have learned: I just tried the same thing, and I got the right query either way. So that's pretty cool.

It's a pretty neat feature and I can see some legitimate value in it. I'm pretty good writing SQL myself... I've managed to write some truly hideously complex queries over the years... but there are definitely instances I can recall where the query didn't seem obvious at the start, and having an AI that can MAYBE produce something that is AT LEAST a starting point is definitely something I can get onboard with.

DBeaver is probably the best, most underrated UI for interacting with relational databases, that's free and universal.
It's just sad that I had to try out literally everything else, which is total crap in comparison, before I stumbled upon DBeaver.

Who asked for RedDatabase and RedXpert? You guessed it - nobody 😑 It's a buggy Firebird and DBeaver domestic knock-off!

My student was assigned with making Flask app by "simple" requirements. But guess what? We can't figure out hecking RedDatabase?! Figures out that they sent incompatible *.fdb database file, on which we wasted entire 3 hours troubleshooting obscure error, while clean database doesn't cause any trouble.

Last error that completely drained us is following:
"""
Reason: unsupported on-disk structure for file /var/rdb/test.fdb; found 12.3, support 12.2; IProvider::attachDatabase failed when loading mapping cache [SQLState:HY000, ISC error code:335544379]
"""

So now, he basically recreates database by scheme on image. What also shady seems to me is that application also has to deployed on virtual OS which he can bring on USB stick or by cloud later.

Is it me or DBeaver is plain shit and not-so-robust on importing to csv?

In a table that contains bizzare character as: " & + / ( ) ;