[REQ] Environment warning signs

[GoogleCodeExporter]

Can we please have the ability to set a particular connection such that it 
shows big ugly warning signs on the window for that connection?  I have a 
live and a test server with open connection to each, it'd be nice if the live 
window had big yellow-and-black stripes on it or something to show that it's 
a dangerous server.  That, or perhaps we can set a "read-only" to be sure no 
inserts or updates or deletes or alters get executed?

Ta,

Original issue reported on code.google.com by kevin.li...@gmail.com on 29 Jul 2009 at 10:53

[GoogleCodeExporter]

This has been open for a couple of years now. Any inkling as to when it will be 
available? Thanks

Original comment by brantley...@gmail.com on 3 Apr 2013 at 1:45

[GoogleCodeExporter]

I too would like this prioritized, as was stated in the first request. Having 
test and live databases side by side - with the same content - is a recipe for 
error. Coloring the tabs would be my ideal option. 

Original comment by possibil...@gmail.com on 28 Jun 2013 at 5:44

[GoogleCodeExporter]

+1 for this. Really Really required.

Original comment by abhishek...@gmail.com on 30 Jul 2013 at 2:31

[GoogleCodeExporter]

+1 Agree. All other SQL editors can do it. It should be prioritised!

Original comment by kasperha...@gmail.com on 30 Jul 2013 at 2:34

[GoogleCodeExporter]

I'd be thrilled to see this as a feature as well.  Any implementation would be 
better than none.

Original comment by au...@asu.edu on 17 Sep 2013 at 12:34

[GoogleCodeExporter]

+1 for read-only mode or the ability to require confirmations for write actions 
for certain connections.

Original comment by ja...@builtbymoby.com on 17 Oct 2013 at 9:52

[GoogleCodeExporter]

I'm happy, if they just color the tab.. :-/

Original comment by kasperha...@gmail.com on 18 Oct 2013 at 6:55

[GoogleCodeExporter]

I agree. Coloring the tab should be an effective low-hanging fruit - Please 
implement that before considering doing complex read-only/prompt stuff.

Basically anything that lets me effectively see that I am on a 
production/development environment!

Original comment by larsm...@gmail.com on 18 Oct 2013 at 7:18

[GoogleCodeExporter]

Maybe some of you have already noticed, r4129 includes basic tab colors.
You can download this EXPERIMENTAL version from: http://nightly.sequelpro.com
But *** PLEASE BACKUP THIS FILES FIRST *** before trying it:
~/Library/Application Support/Sequel Pro/Favorites.plist
~/Library/Preferences/com.sequelpro.SequelPro.plist

Original comment by schlabbe...@gmail.com on 25 Oct 2013 at 11:13

[GoogleCodeExporter]

tested r4135 .. that's what i want!! 

Original comment by m...@robert-haensel.com on 8 Nov 2013 at 10:38

[GoogleCodeExporter]

r4135 is definitely a step in the right direction - but it's only a half 
solution. Or am I missing something? Do you HAVE to have tabs open to see the 
color - What if I for some reason prefer two windows?

Original comment by larsm...@gmail.com on 8 Nov 2013 at 1:37

[GoogleCodeExporter]

The tab color is a must-have feature, shouldn't be a split between issues like 
read/only access or whatever it takes for some people and simple tab coloring 
(which is already working) ?

If it's already fully working, could it be in the next milestone and then we 
could have it with the next release ?

The other issue is something else : there has been a kind of mix between 
warning and preventing IMHO.

The color is great for warning, and for my use it's sufficient. (I understand 
that some people need more advanced settings)

Original comment by olivier....@aircastnet.ca on 15 Jan 2014 at 10:26

[GoogleCodeExporter]

This issue is now managed at GitHub:
https://github.com/sequelpro/sequelpro/issues/346

Any comments made here will be ignored.

Original comment by schlabbe...@gmail.com on 16 Jan 2014 at 7:55

• Added labels: GHM