On Mon, Mar 7, 2011 at 6:21 AM, Guillaume Lelarge
> Well, it was supposed to be deleted. Actually, I was supposed to ask if
> anyone knows why there is the "if (sql.IsNull())" check at all (the "||
> forceRefresh" is a test I should have deleted). I have no idea why there
> is this sql.IsNull() test. It doesn't appear in other same sources.
> Dave, any idea?
It's an optimisation to prevent us regenerating the SQL every time we
need it. For most objects that's cheap - for some (eg. tables) - far
When refreshing, frmMain->Refresh calls the SetDirty() function on the
object, which causes sql to be cleared ready for regeneration.
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
In response to
pgadmin-hackers by date
|Next:||From: Dave Page||Date: 2011-03-07 13:55:46|
|Previous:||From: Dave Page||Date: 2011-03-07 06:27:39|
|Subject: Re: Feature: visual feedback of disabled triggers|