| 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:38:22 |
| Message-ID: | 7581.1015274302@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:
> On 4 Mar 2002 at 14:24, Tom Lane wrote:
>> ... but I'm a little worried about the possibility of errors
>> in loading schemas from existing databases, where there might be
>> non-unique constraint names.
> Create a tool to generate unique constraint names during a dump.
And then all we need is a time machine, so we can make existing
instances of pg_dump contain the tool? It's not that easy ...
I am not sure that there's really a problem here, because I don't
think duplicate constraint names will be generated during plain
CREATE operations. However, an ALTER TABLE might leave you with
a problem. Hard to tell if this is critical enough to worry about.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Barnard | 2002-03-04 20:41:42 | Re: Uniqueness of rule, constraint, and trigger names |
| Previous Message | Eric Scroger | 2002-03-04 20:28:57 | JDBC: java.sql.SQLException: results returned |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Barnard | 2002-03-04 20:41:42 | Re: Uniqueness of rule, constraint, and trigger names |
| Previous Message | Hubert Palme | 2002-03-04 20:34:25 | PL/pgSQL Syntax Problem |