| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Michael Shapiro <mshapiro51(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Aren Cambre <aren(at)arencambre(dot)com>, pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Foreign key UI bug |
| Date: | 2010-11-20 15:09:27 |
| Message-ID: | 4CE7E4A7.1050804@lelarge.info |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Le 20/11/2010 15:15, Michael Shapiro a écrit :
> Theoretically, you could have the same problem with the primary key -- there
> could be an index with that name already.
If it happens, it would be PostgreSQL fault, not pgAdmin. The name of
the constraint and the name of the index, in a primary key and in a
unique contraint, are determined by PostgreSQL, not pgAdmin. On the
contrario, the name of the index of a foreign key is determined by
pgAdmin because this is not a PostgreSQL feature.
> But in practice it doesn't happen. You could generate a name for the foreign
> key based on similar pattern for the pk
> and if it fails, then it falls on the user to provide a name. Seem like it
> would work 99% of the time.
>
I guess Magnus's idea is the good one (fk_tablename_columnname).
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2010-11-20 17:48:46 | Re: Foreign key UI bug |
| Previous Message | Michael Shapiro | 2010-11-20 14:15:13 | Re: Foreign key UI bug |