From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Erwin Brandstetter <brandstetter(at)falter(dot)at> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: More refresh issues |
Date: | 2007-09-10 09:23:36 |
Message-ID: | 46E50D18.8030802@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Erwin Brandstetter wrote:
> That doesn't seem to work in the table subtree, yet. :/
> After deleting ... --> focus goes to ...
> ... table column --> a random collection node in this table subtree.
> ... a check or fk constraint --> a unique constraint
> ... a unique constraint --> the pk constraint
> ... a trigger --> a table column
> ... an index --> the colums collection
> Other results with other tables. Behavior seems random. In pg 8.1 and pg
> 8.2 alike.
Gah, stupid error - and pure chance it worked OK when I tested it!!
Fixed in SVN.
> Also, if deletion fails (because of fk constraint or something) the
> focus will still wander. Could this be constricted to successful deletion?
> This is not constricted to the table subtree.
Also fixed.
> To sum it up, the policy on refreshing objects in the tree is now:
> pgAdmin updates all (well, almost) affected objects after changes made
> per dialog. This does not cover changes via manual SQL or from other
> users or other clients. I would generally recommend to refresh objects
> before working on them in such environments.
> Might be worth a note in the help file somewhere.
Patches are welcome :-)
Cheers, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-09-10 12:06:00 | Re: two minor things |
Previous Message | svn | 2007-09-10 09:21:43 | SVN Commit by dpage: r6630 - trunk/pgadmin3/pgadmin/frm |