'SET SQLPROMPT' command window

[Bruce Carson]

Can I 'SET SQLPROMPT' in the command window in pl/sql developer like you would for sql*plus?

 

[CTzen]

There is a similar command

SQL> set prompt sql
sql> set prompt [db]
DB.EXEDRA.DOMAIN.COM> set prompt [user]
SLAVA> set prompt [connection]
SLAVA@DB.EXEDRA.DOMAIN.COM>

 

[Marco Kalter]

We'll add SET SQLPROMPT support as well.

 

[CTzen]

That's a very good news. Also if you plan to keep 'set prompt', could you please make [db],[user],[connection] optionally in lower case. For example [USER]->SLAVA and [user]->slava.

For now my new prompt looks like this

SQL> set prompt :-
:-> select '<-:' as "prompt twin" from dual;

prompt twin
-----------
<-:

Executed in 0.281 seconds

:->

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[RobertK]

heheh so exactly 2 years after I first asked about this in this thread
this feature is still not available

 

[CTzen]

heheh, it is available now ... kind of

Enhancements in PL/SQL Developer 7.0.2
======================================
...
- Command Window: SET SQLPROMPT added (same as SET PROMPT) with case sensitive [params]
...

 

[Marco Kalter]

heheh so exactly 2 years after I first asked about this in this thread
this feature is still not available [Roll Eyes]

No, the feature has been available as SET PROMPT since August 2004. We had never realized that the correct syntax is SET SQLPROMPT though, which we have now corrected.

 

[Aviga]

Hello,

I use a SQLPATH variable both with SQL*Plus and PL/SQL Developer. I am trying to set the SQL PROMPT on both environments.

set sqlprompt "&variable"
does not work (yet?) with PL/SQL Developer.
(By the way, we may now even omit "&" prefix when referencing substitution variables with "set sqlprompt" command from SQL*Plus version 10.1.)

This is very annoying since
set sqlprompt [connection]
is obviously not recognised by SQL*Plus.

Would you have a plan to fully include this feature in PLSQLDev?

Thanks in advance.

Best regards,

A.

 

[Marco Kalter]

The next version supports SET SQLPROMPT. Right now you will have to use SET PROMPT instead, which can be a problem for scripts that need to run both in SQL*Plus and PL/SQL Developer.

 

[Aviga]

Thanks. Actually, I found a workaround: I do a "set sqlprompt &variable" first, then a "set prompt [connection]" in my login.sql script.

In SQL*Plus, the first command works, but the second one does nothing.
In PL/SQL Developer, the first command replaces the SQL prompt by a variable name instead of its value, but the second command works.

 

[BRi-17]

After Upgrading to PLD 11.0.5.1775 the feature isn't working any more.

My "login.sql" in the PLD folder:
set prompt [connection]

Prompt in the command window:
SQL>

When I type in in the command window console "set prompt [connection]" the prompt is renamed to the connection name, but not when I open a new command window.

Could you please fix it?

Best regards Berit

 

[Marco Kalter]

We'll fix it.