| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | dan(at)langille(dot)org |
| 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:47:52 |
| Message-ID: | 7683.1015274872@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
"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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Langille | 2002-03-04 20:50:39 | Re: Uniqueness of rule, constraint, and trigger names |
| Previous Message | Bruce Momjian | 2002-03-04 20:46:56 | Re: elog() patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Langille | 2002-03-04 20:50:39 | Re: Uniqueness of rule, constraint, and trigger names |
| Previous Message | Dan Langille | 2002-03-04 20:43:38 | Re: Uniqueness of rule, constraint, and trigger names |