Qrulla Docs

Safety and administration

Working on production

Qrulla's protections so you don't slip on an important database: confirmations, preview, undo and hidden sensitive data.

Mark your production connections

In the connection, choose Environment: Production. From then on, every dialog that changes something on it (paste, import, compare, generate test data, drop…) says so in large type, and the confirmation of anything that deletes always says which connection and environment it happens on. Give it a color too, to recognize it in the tree.

Confirmations

On any connection, nothing that deletes data or objects runs without your confirmation:

  • in the editor, DROP, TRUNCATE, DELETE or UPDATE without WHERE, and replacing an existing object;
  • in the tree, dropping, emptying or truncating;
  • when pasting or importing, replacing what exists;
  • in the grid, saving changes, which go together in one transaction.

Preview on production

Max plan. Before running an UPDATE or DELETE on a production connection, Qrulla counts how many rows will change and shows you the first ones, without running anything yet. If it's not what you expected, you cancel.

Undo changes

Max plan. Before each UPDATE or DELETE from the editor, Qrulla keeps a copy of the rows it will change, only on your computer and for 7 days. If you made a mistake:

  1. In the editor, click “Undo changes” to see the list of changes you can undo, or “Undo” on that statement's message.
  2. Qrulla checks how the rows are now: how many go back to how they were, how many were already like that and how many someone else changed later.
  3. The ones someone else changed aren't touched, unless you check “Also put back the ones that changed later”.

It works with tables that have a primary key, up to 50,000 rows per statement, in single-table statements (no JOIN). The copies take at most 500 MB. Before running, the editor tells you if a change can't be undone and why.

Turn it on or off in “Preferences” with “Keep a copy to undo UPDATE and DELETE”.

Hide sensitive data

Max plan. When pasting objects with data, for example from production to development, check “Hide sensitive data”. Qrulla looks for columns with personal data and suggests what to write in each one:

email, full name, first name, last name, phone, card, ID document (DUI, DNI, NIT…), address, birth date, IP address, text in the same format, or empty it (NULL).

The fake data is realistic, and the same real value always gives the same fake one, so keys still match across tables. NULL stays NULL. The source doesn't change.

Something missing or unclear? Write to support@qrulla.com.