Sequelpro: When importing a dump into a production database, ask "are you sure?" first

[aacook]

Sometimes I accidentally import a dump into a production database by mistake, when I meant to import into my development environment. This is especially true in the past couple months, after I memorized the cmd+shift+i shortcut. 😅

It would be nice to have a simple flag in the settings for each connection, tagging it as a production database.

That way when I go to import a dump into production by mistake, Sequel Pro can ask, "Are you sure?" 😀

[dmoagx]

Personally I don't think that would be useful.
Experience shows that people will simply develop muscle memory and confirm the message without reading.

I think the only thing we could do is use the connection favorite color (and maybe favorite name) in the export dialog somewhere.

But in general I can only recommend the same thing as always: For production always create two separate mysql user accounts: One with read only permissions and one with read-write permissions.
Do not store the password for the read-write user in Keychain and only use the read-only user for regular tasks.

[necmettin]

I have a connection that allows access to both the development and the production databases. The isProduction filter would have to be not connection based, but server+database based.

[stale[bot]]

This issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale[bot]]

This issue has been auto-closed because there hasn't been any activity for at least 21 days. However, we really appreciate your contribution, so thank you for that! 🙏 Also, feel free to open a new issue if you still experience this problem 👍.