Feature request - Connection dialog and concurrent database connections on same plsqldev instance

Alp

Member
Hi,

First, I currently try plsqldev, i'm currently a [size=8pt]toad user[/size] ;)
plsqldev seems require most of my requested features with a more reasonable price.

  • 1 One usefull feature for me is a rich dialog connection
    it's very usefull when you have a lot of database schema to manage :(
  • 2
    And on a same way, it's not possible to open more than one database connection on the same plsqldev instance, can be this evolve in the future ?

Regards,
 
A dialog like the next (it can be found on some concurrent product :)

User - Database - Last connect - Connect mode - Auto connect - User column1 - User column2 - Oracle Home
scott - mytns - - NORMAL - NO - PROD
systel - mytns - - SYSDBA - NO - PROD

BUTTON CONNECT BUTTON EDIT TNS BUTTON CANCEL
 
That requested feature can be dangerous too.
It should always be made clear in which connection you are in your current window. Otherwise it can be risky when you assume you're in development environment while forgetting that you've just switched into production environment for a quick check.
I'm sure all of us have had moments of shocks like that.
Would be great if there could be some color coding of i.e. the windows title bar for that, something like prod=red, test=blue, dev=green, unknown=yellow. It should in any case be something that draws attention to it automatically and intuitively.
 
The 'Color Coding' feature is already present. Look under Preferences/User Interface/Appearance/Connection Indicators. I use Red for my Prod databases, Green for my Dev databases.

Cheers,
Pete.
 
Indeed it exists (though I wasn't using it; thanks Pete for reminding me about it).

Is it possible to use wildcards in the 'match' (user@database)? %@PROD% for example. If not I hope Marco puts it in the requests list :)
 
Try using something like this, it seem to work

ex:
bc*@*

This will display my color code for any user starting with BC on any database
 
Thank you guys for the tip. Is just a bit counter-intuitive for us Oracle users to have to use '*' as wildcard. I'd prefer the standard sql-query LIKE syntax with '%' and '_' as wildcards. :cool:
 
Back
Top