r/SQL • • 2d ago

Discussion I built a free native Windows SQL client because DBeaver felt too heavy

Post image

I write SQL all day and got tired of waiting on Java and Electron apps, so I wrote RimestDB with WinUI 3 and .NET. On my machine it opens in about 2 seconds and uses 66 MB with a connection open. DBeaver on the same machine and database: 11 seconds and 338 MB (warm start, memory as shown in Task Manager).

It works with PostgreSQL, SQL Server, MySQL/MariaDB and SQLite.

Things I built for my own prod habits: manual commit mode per connection, a confirmation before UPDATE/DELETE without WHERE, and in manual mode read-only SELECTs don’t open a transaction, so browsing data doesn’t leave a lock that holds up a migration.

It’s free, with no account and no time limit. There’s also an optional paid Pro tier. Windows 10/11 only.

I’d like blunt feedback from people who live in a DB client: what would stop you from switching?

db.rimest.com

0 Upvotes

10 comments sorted by

3

u/ravushimo 2d ago

...and ofc it's behind subscription.

1

u/EmirVivident 2d ago

There's a subscription option, but you can use the free version for life. The subscription fees are also reasonable.

3

u/ravushimo 1d ago edited 1d ago

With limits of 3 tabs and 1 connection this is at most a trial.

> subscription fees are also reasonable

In a vacuum where your software is the only one that is behind sub and no alternatives exist, I would reluctantly agree, but in this age? No, it's not.

1

u/Discordbothost 1d ago

how do you decide which SELECTs can run outside the manual transaction? PostgreSQL's SELECT ... FOR UPDATE needs to stay in it. i'd want an example showing a locking read, an update and rollback all using the same transaction before trusting it for prod work.

1

u/EmirVivident 1d ago

Good question. The rule is conservative: a SELECT skips the transaction only when no transaction is open yet and it’s a plain read: no FOR (UPDATE/SHARE), INTO or LOCK, and no function calls outside a small allowlist of built-ins like count() or lower(). Anything else opens the transaction. Once a transaction is open, every statement runs inside it, plain SELECTs included, so you see your own uncommitted changes.

So in manual commit mode:

SELECT * FROM accounts WHERE id = 1 FOR UPDATE;  -- opens the transaction, row is locked
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
SELECT balance FROM accounts WHERE id = 1;       -- same transaction, sees the new value

then Rollback undoes it and releases the lock. All three run on one connection in one transaction. If you try it, I’d love to hear how it behaves for you.

6

u/omniuni 2d ago

It seems SQL clients are just a step behind download managers and music players in the list of vibe coded projects.

2

u/Pink_Slyvie 2d ago

I just use CLI..... I organize my scripts into folders.

1

u/getlatch 2h ago

Here is my mac app as well. It is feature rich currently support MS SQL Server only. Free during beta.
https://datastudio.luklalogic.ai/

1

u/arwinda 2d ago

It's not CLI.

Eventually your tool will have to support more than just the current set of very basic features. And grow to what DBeaver is.