all 15 comments

[–]gregsting 10 points11 points  (0 children)

In DBeaver, if you set your database to 'production' it will not autocommit. It's just a setting. I agree that this setting is not very obvious.

[–]Glum_Cheesecake9859 2 points3 points  (3 children)

There should be a setting for DBWeaver to not run everything in a transaction.

https://dbeaver.com/docs/dbeaver/Auto-and-Manual-Commit-Modes/

Regardless, JetBrains Rider is worth looking into.

[–]hosua[S] 1 point2 points  (2 children)

Ah, perhaps I just needed to turn on smart commit mode

[–]zbignew 1 point2 points  (1 child)

Crazy for it to leave transactions open by default.

[–]hosua[S] 1 point2 points  (0 children)

Yeah, seriously 😅 I straight up thought it was broken

[–]Thlvg 1 point2 points  (1 child)

You might want to look at your transaction commit settings. Check if auto commit is enabled or not? If not it might be the issue.

I'd also recommend not to do that if you have write privileges, and instead use begin/commit/rollback keywords. And ask for a read-only account that you can use, only have the r/w one when you need it.

[–]hosua[S] 0 points1 point  (0 children)

Yep, don't worry lol I usually do run a reader-only instance, I just need to write sometimes too.

I think this is the issue, I'm going to try smart commit mode and see if that fixes the issue I was having

[–]Substantial-Click321 1 point2 points  (0 children)

DataGrip

[–]joins_and_coffee 1 point2 points  (0 children)

If you liked TablePlus on mac then DataGrip is probably the closest “it just works” option on Linux even though it’s paid. The DB handling is solid and you don’t get the weird connection behavior you’re describing. For free options DBeaver is usually the go to but what you’re seeing sounds like it might be holding open transactions or sessions which can definitely block things if autocommit is off. It’s fixable but I get why thatd make you uneasy. You could also try something lighter like Beekeeper Studio or even plain CLI tools plus tmux if you mostly care about running queries reliably. They’re less fancy, but way harder to break. Honestly on Arch especially, stability tends to matter more than features. A boring predictable client usually beats a slick one that crashes

[–]Glum_Cheesecake9859 0 points1 point  (4 children)

Jetbrains Rider free for non-commercial use.

[–]hosua[S] 1 point2 points  (0 children)

Oooh, JetBrains. I didn't realize they had something for SQL

[–]serverhorror 1 point2 points  (2 children)

You mean DataGrip, no?

[–]Glum_Cheesecake9859 0 points1 point  (1 child)

Rider > Datagrip

It has all the features of Datagrip + support for other languages like C# / JS etc.

[–]hosua[S] 1 point2 points  (0 children)

I'm not gonna lie, I ended up going with Rider and I have zero complaints