Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Enhancement SQL*Plus (prev.: Re: Fixing a little problem in the login.sql script found in Tom Kyte's book)

Re: Enhancement SQL*Plus (prev.: Re: Fixing a little problem in the login.sql script found in Tom Kyte's book)

From: <Christopher.Jones_at_oracle.comX>
Date: 17 Jan 2003 11:33:26 +1100
Message-ID: <u8yxk1up5.fsf@oracle.comX>


"Peter van Rijn" <p.vanrijnREMOVE_at_THISzhew.nl> writes:
> Thanks for your comments. It certainly is an enhancement, but
> what I really meant was an enhancement of the prompt itself. If
> the prompt is set to use a variable it should be reset every
> time a connect command has been used. If I understand you well
> this has not (yet?) been realized.

We're listening and Alison didn't give away all the good news, but I don't want to comment on futures in detail.

Note the web based iSQL*Plus 9.2 already displays the current username and connect identifier in the status line.

A comment on SQL*Plus changes: It is always hard to bring in features when someone, somewhere will complain their application is broken by the change. In SQL*Plus 9.0 we introduced the SET SQLPLUSCOMPATIBILITY option to cater for the RDBMS redefinition of NCHAR and to give us a little leeway to make future changes.

In general, SQL scripts will be more portable if they explicitly set SQLPLUSCOMPATIBILITY. The next version of SQL*Plus will have an equivalent "-C" command-line option to make it easier to use (OK, I just did mention more futures!)

Chris

--
Christopher Jones, Oracle Corporation, Australia.
Received on Thu Jan 16 2003 - 18:33:26 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US