| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Support for invalid foreign keys |
| Date: | 2011-03-07 06:49:02 |
| Message-ID: | AANLkTi=SPK90pyqJbhx28q08+VH_VuE6A2m-O0H1SP2u@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Mon, Mar 7, 2011 at 6:21 AM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> 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
from it.
When refreshing, frmMain->Refresh calls the SetDirty() function on the
object, which causes sql to be cleared ready for regeneration.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2011-03-07 13:55:46 | s/xpm/png/g |
| Previous Message | Dave Page | 2011-03-07 06:27:39 | Re: Feature: visual feedback of disabled triggers |