Dave Page wrote:
>
>
>>-----Original Message-----
>>From: Dave Page
>>Sent: 06 October 2003 10:17
>>To: Matej Rizman; pgadmin-support@postgresql.org
>>Subject: Re: [pgadmin-support] PgAdmin III: Two bugs
>>
>>
>>Hi Matej
>>
>>
>>
>>>-----Original Message-----
>>>From: Matej Rizman [mailto:matej.rizman@guest.arnes.si]
>>>Sent: 05 October 2003 23:37
>>>To: pgadmin-support@postgresql.org
>>>Subject: [pgadmin-support] PgAdmin III: Two bugs
>>>
>>>
>>>
>>>PgAdmin III version: 1.0.0
>>>
>>>First bug:
>>>Creating UNIQUE constraint executes ALTER TABLE ... ADD
>>>CONSTRAINT asfd PRIMARY KEY ....
>>>
>>>
>>I cannot reproduce that - what steps did you take?
>>
>>
>
>Scrub that, I see it. If you right click and then create New Unique
>Constraint then you get a primary key, however if you do it from the
>table properties dialgoue (as I do) it works fine apart from another
>bugette in which the anem is doubled (ie frog becomes frogfrog).
>
>Andreas; can you take a look at this please? I've spent a while on it
>but haven't figured it out and need to get on with some paid work (and
>you'll no doubt fix it in a few minutes :-))...
>
Fixed in head and branch. dlgIndexConstraint::GetSql() was hard-coded to
"PRIMARY KEY" instead of wxString(typeList[objectType].typeName).Upper().
Regards,
Andreas
