Re: How to rename a schema

On Wed, 19 Mar 2003 20:41:43 +0100, Frank <fvanbortel_at_netscape.net> wrote:

>Ed Stevens wrote:
>> On Wed, 19 Mar 2003 18:29:52 +0800, "Timmy Sin" <tswsin_at_yahoo.com>
>> wrote:
>>
>>
><snip!>
>>>
>>>Regards,
>>>Timmy
>>>
>>
>>
>> My first question is "'why?" Why do you want to change the name of
>> the schema owner in a cloned db? There may very well be good reasons,
>> but I get the impression from what you've said so far that it is
>> simply because it is in another db. Not a good reason. In fact, if
>> I've got a 'cloned' database (like a test copy of production) I
>> *don't* want things renamed from one DB to the other. You are making
>> extra work for yourself now, and possibly a lot of extra work down the
>> road.
>
>Because of naming conventions? Which are there because of
>protection against user / developer errors?
>If I try to logon to a test/development database and have to find
>out the hard way that I dropped tables in production, I'd rather have
>a TEST user owing all objects in that environment, and a PROD user
>owning them in production.
>The ora-01017 would have triggered me that I was (attempting to)
>scribble the production instance.

Point taken. I guess this falls under the headings of "101 Ways to Skin a Cat, or Choose Your Poison." A problem is perceived, a solution is chosen from multiple options, and once THAT choice is made, other problems flow from it and THOSE problems are the ones we continue to grapple with, seldom questioning our original assumption or even realizing that it was an assumption that *could* have been solved differently.

Hmm. How's that for an overly-long stream-of-conciousness sentence? With a little practice I could become as difficult a read as H. Melville. ;-) Received on Wed Mar 19 2003 - 14:02:19 CST