Re: Fw: OT - Getting fired for database oops
From: Jared Still <jkstill_at_gmail.com>
Date: Thu, 21 May 2009 09:16:57 -0700
Message-ID: <bf46380905210916i1cf9d714m71ed20e4ed2e6c88_at_mail.gmail.com>
On Thu, May 21, 2009 at 8:24 AM, Bobak, Mark <Mark.Bobak_at_proquest.com>wrote:
Date: Thu, 21 May 2009 09:16:57 -0700
Message-ID: <bf46380905210916i1cf9d714m71ed20e4ed2e6c88_at_mail.gmail.com>
On Thu, May 21, 2009 at 8:24 AM, Bobak, Mark <Mark.Bobak_at_proquest.com>wrote:
> Jared,
>
>
>
> Starting in 10g, you can do:
>
> Set sqlprompt “_user’_at_’_connect_identifier> “
>
> And it will stay up to date across multiple ‘connect’ operations.
>
>
>
Thanks Mark, I do recall that.
It is another example of 'tool little too late'
I already had a method to deal with it.
Exiting sqlplus to make a new connection is actually simpler, at least for me.
This how curmudgeons are created.
"I crafted a solution to that problem years ago, and 10 years later they come out with a solution?"
Bah, humbug!
:)
Jared
-- http://www.freelists.org/webpage/oracle-lReceived on Thu May 21 2009 - 11:16:57 CDT