Le 21/11/2010 00:12, Aren Cambre a écrit :
>>
>> The simple patch attached forces one to type either the constraint name
>> or the index name. Which seems enough for me.
>>
>
> That sounds like a good resolution.
>
Thanks. Commited. Should be in 1.12.2.
--
Guillaume
http://www.postgresql.fr
>
> The simple patch attached forces one to type either the constraint name
> or the index name. Which seems enough for me.
>
That sounds like a good resolution.
Aren
Le 20/11/2010 16:09, Guillaume Lelarge a écrit :
> 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
>
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
Theoretically, you could have the same problem with the primary key -- there
could be an index with that name already.
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. S
Le 20/11/2010 12:39, Magnus Hagander a écrit :
> On Sat, Nov 20, 2010 at 12:37, Guillaume Lelarge
> wrote:
>> Le 20/11/2010 12:27, Magnus Hagander a écrit :
>>> On Sat, Nov 20, 2010 at 12:24, Guillaume Lelarge
>>> wrote:
Le 20/11/2010 04:50, Aren Cambre a écrit :
> I found a UI bug whe
On Sat, Nov 20, 2010 at 12:37, Guillaume Lelarge wrote:
> Le 20/11/2010 12:27, Magnus Hagander a écrit :
>> On Sat, Nov 20, 2010 at 12:24, Guillaume Lelarge
>> wrote:
>>> Le 20/11/2010 04:50, Aren Cambre a écrit :
I found a UI bug when creating a foreign key.
When creating a prima
Le 20/11/2010 12:27, Magnus Hagander a écrit :
> On Sat, Nov 20, 2010 at 12:24, Guillaume Lelarge
> wrote:
>> Le 20/11/2010 04:50, Aren Cambre a écrit :
>>> I found a UI bug when creating a foreign key.
>>>
>>> When creating a primary key, all you have to do is select the column in the
>>> *Colum
On Sat, Nov 20, 2010 at 12:24, Guillaume Lelarge wrote:
> Le 20/11/2010 04:50, Aren Cambre a écrit :
>> I found a UI bug when creating a foreign key.
>>
>> When creating a primary key, all you have to do is select the column in the
>> *Columns* tab of the dialog. You don't have to fill out any oth
Le 20/11/2010 04:50, Aren Cambre a écrit :
> I found a UI bug when creating a foreign key.
>
> When creating a primary key, all you have to do is select the column in the
> *Columns* tab of the dialog. You don't have to fill out any other fields;
> pgadmin appears to take care of this for you.
>
I found a UI bug when creating a foreign key.
When creating a primary key, all you have to do is select the column in the
*Columns* tab of the dialog. You don't have to fill out any other fields;
pgadmin appears to take care of this for you.
It seems then that with a foreign key, all you should h
11 matches
Mail list logo
