> -----Original Message-----
> From: Andreas Pflug [mailto:[EMAIL PROTECTED] 
> Sent: 06 October 2003 16:48
> To: Dave Page
> Cc: Matej Rizman; [EMAIL PROTECTED]
> 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.


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to