| From: | "Dan Langille" <dan(at)langille(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, pgsql-sql(at)postgreSQL(dot)org |
| Subject: | Re: Uniqueness of rule, constraint, and trigger names |
| Date: | 2002-03-04 20:50:39 |
| Message-ID: | 200203042050.g24Kogk80096@lists.unixathome.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
On 4 Mar 2002 at 15:47, Tom Lane wrote:
> "Dan Langille" <dan(at)langille(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-03-04 21:05:16 | Re: Database Caching |
| Previous Message | Tom Lane | 2002-03-04 20:47:52 | Re: Uniqueness of rule, constraint, and trigger names |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-03-04 21:40:16 | Re: [HACKERS] Uniqueness of rule, constraint, and trigger names |
| Previous Message | Tom Lane | 2002-03-04 20:47:52 | Re: Uniqueness of rule, constraint, and trigger names |