From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | "Matej Rizman" <matej(dot)rizman(at)guest(dot)arnes(dot)si>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: PgAdmin III: Two bugs |
Date: | 2003-10-07 07:12:42 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B764@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 06 October 2003 16:48
> To: Dave Page
> Cc: Matej Rizman; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] PgAdmin III: Two bugs
>
>
> >
> >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().
Cool, thanks. Did you get the frogfrog thing as well? I noticed that
when adding a UNIQUE constraint from the table prop dialogue.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-10-07 07:27:04 | Re: PgAdmin III: Two bugs |
Previous Message | Tom Lane | 2003-10-07 04:01:58 | Re: 7.4beta4: make check broken? |