On Sat, May 3, 2008 at 12:57 AM, Erwin Brandstetter
> - <tab> key now seems to have the same effect as moving to the next field
> with the mouse pointer. This is a twofold improvement: no data loss,
> behavior unified.
> The false warnings have consequently become more frequent. It is the lesser
> evil, if we have to chose.
> - Save warning now fires, if I engage sort/filter, which prevents data loss.
> It might be even smarter to wait until sort/filter is actually applied. If
> one just wants to look up the filter or decides to [CANCEL] for any other
> reason, then we may not need the warning. But that's a minor point.
> - [Cancel] or [OK] now abort or apply sort/filter just the way it should be
> I've also checked for the other stuff I have reported recently and replied
> on the thread where I've come up with something.
> The rest seems to work like a charm now. Also no crashes or anything bad and
> - Rule privilege for VIEWs: partly fixed, see reply on thread.
> - Refresh object name: seems FIXED.
> - "FORCE" option for REINDEX: seems Robins FIXED it.
> - Redundant double-quotes in types: seems FIXED.
> - Errors & notices in pgAdmin log-files: seems FIXED.
Wow, that's quick work. Thanks for the usual high standard of testing
- I'll check the rule priv thing in a couple of days. guess I just
overlooked a spot - patience never was my strong point.
EnterpriseDB UK: http://www.enterprisedb.com
In response to
pgadmin-hackers by date
|Next:||From: svn||Date: 2008-05-03 20:03:22|
|Subject: SVN Commit by dpage: r7269 - trunk/pgadmin3/pgadmin/schema|
|Previous:||From: Erwin Brandstetter||Date: 2008-05-02 23:57:50|
|Subject: Re: Behavioral issues in data grid: unsaved data,