Thread: Re: [SQL] Uniqueness of rule, constraint, and trigger names

"Dan Langille" <dan@langille.org> writes:
> It would be easily detected at load time.  Then you direct the user to the 
> tool mentioned above.

But if the user has already dumped and flushed his old installation,
he's still in need of a time machine.

Hmm, maybe what we need is a tool that can be applied during load.
Essentially, alter incoming constraint names as needed to make them
unique.  We could have this enabled by a SET switch...
        regards, tom lane

On 4 Mar 2002 at 15:47, Tom Lane wrote:

> "Dan Langille" <dan@langille.org> writes:
> > It would be easily detected at load time.  Then you direct the user to
> > the tool mentioned above.
> 
> But if the user has already dumped and flushed his old installation,
> he's still in need of a time machine.

Agreed.  I had that same problem with upgrading to 7.2.  My solution was 
to install 7.1.3 on another box, load, massage, dump.  Next time, I'll 
keep the old version around a bit longer.

> Hmm, maybe what we need is a tool that can be applied during load.
> Essentially, alter incoming constraint names as needed to make them
> unique.  We could have this enabled by a SET switch...

I think that is an eloquent solution.
-- 
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples