Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3: . src/dlg - Mailing list pgadmin-hackers

From Dave Page
Subject Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3: . src/dlg
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9402@ratbert.vale-housing.co.uk
Whole thread Raw
In response to SVN Commit by dpage: r4380 - in trunk/pgadmin3: . src/dlg  (svn@pgadmin.org)
Responses Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3:  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 21 July 2005 10:12
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] SVN Commit by dpage: r4380 -
> in trunk/pgadmin3: . src/dlg
>
> svn@pgadmin.org wrote:
> > Author: dpage
> > Date: 2005-07-21 09:26:58 +0100 (Thu, 21 Jul 2005)
> > New Revision: 4380
> >
> > Modified:
> >    trunk/pgadmin3/CHANGELOG.txt
> >    trunk/pgadmin3/src/dlg/dlgTable.cpp
> > Log:
> > Prompt the user before removing columns, constraints or
> inherited tables in the table dialogue,
>
> At least the "ask when deleting" setting should be observed.

I didn't know we even had such an option. Will fix.

> It's still
> questionable, since these removes aren't executed immediately, but
> collected until OK is pressed.

Not when creating a new object. It's a real pita when you've defined a
30 column table then accidently delete the first one. Even when editting
an existing object it can be a pita if you've made a bunch of other
changes.

/D

pgadmin-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3:
Next
From: Andreas Pflug
Date:
Subject: Re: SVN Commit by dpage: r4380 - in trunk/pgadmin3: