Erwin Brandstetter wrote:
> dpage(at)postgresql(dot)org wrote:
>> Erwin Brandstetter wrote:
>>> 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 :-)
> Not sure what the preferred form for that patch is, as I have not messed
> with source code yet.
diff -u works for me (svn doesn't seem to do -c which is unfortunate).
But hey, whatever the format, I got some code out of Erwin - today is a
*good* day :-)
> I would add a paragraph to
> before the line "<H3>Getting started</H3>":
> <P>pgAdmin is bandwidth friendly. The status of objects in the browser
> is only refreshed on request or after changes made with the built-in
> tools. Be aware that this does not cover changes made via manual SQL or
> from other users or other clients. It is generally advisable to refresh
> objects before working on them in such environments.</P>
Committed - thanks.
> We could add more detail, but I tried to be brief. Also, I am sure you
> are aware that I am not a native English speaker.
Not that you'd notice :-)
In response to
pgadmin-hackers by date
|Next:||From: Erwin Brandstetter||Date: 2007-09-10 15:51:35|
|Subject: Re: More refresh issues|
|Previous:||From: svn||Date: 2007-09-10 15:25:56|
|Subject: SVN Commit by dpage: r6636 - trunk/pgadmin3/docs/en_US|