Environments

✓ functional

Make development, staging, and production unmistakable variants of the same target.

An Environment marks which version of a target a connection uses: Local, Dev, Test, Staging, or Production. It gives the important question - “is this production?” - a clear answer before you run anything.

Assigning an environment

Use the connection editor's PROD / STAGE / TEST / DEV / LOCAL control to set the environment; select it again to clear it. Dev, Test, Staging, and Production come ready with their own colors and icons, which appear as badges in the explorer and status bar.

Safety that rides the environment

Production forces SELECT-only and rollback-wrap on, marks the connection production, and shows a PRODUCTION chip in the status bar - keeping writes locked until you deliberately unlock them for a timed window.
Staging forces rollback-wrap on.
Lower environments add no restrictions - and these defaults only ever turn safety on.

Need an exception? A per-connection production override (Inherit / Production / Not production) has the final say on the production flag.

SQLly environment badges including a production chip — Environment variants of one target, with the production connection badged in the status bar.

Color prod an angry red. Give each environment its own color and the difference reaches your peripheral vision before it reaches your fingers.