Menu

How do you keep yourself from running the wrong UPDATE on production? Here's what I built into my client
📰

How do you keep yourself from running the wrong UPDATE on production? Here's what I built into my client

#sql#redditsql#nicedb#without#connection
Reading 0:00
15s threshold

Everyone has a story about an UPDATE without a WHERE, or the right query in the wrong tab. I built NiceDB, an open-source database client, around that problem:

a production connection is marked everywhere it appears (tree, tab, title bar, status line) and opens read-only;

writing unlocks for ten minutes with the time left in view, then locks again by itself;

before a change is applied, it shows what it touches and asks you to type the connection’s name;

UPDATE and DELETE without WHERE, DROP and TRUNCATE ask before they run;

every statement that changed something is logged with who, when, where and how many rows.

Each step can be configured. All writes go through one place in the core, so no screen can skip it.

It works with PostgreSQL, MySQL, SQL Server, Oracle, SQLite and others. Free, GPL-3.0: https://github.com/maxib0n/NiceDB , with a browser demo at https://nicedb.app .

What do you do today: separate users, read-only replicas, a habit?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.