Re: Support for invalid foreign keys - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Support for invalid foreign keys
Date
Msg-id AANLkTi=SPK90pyqJbhx28q08+VH_VuE6A2m-O0H1SP2u@mail.gmail.com
Whole thread Raw
In response to Re: Support for invalid foreign keys  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: Support for invalid foreign keys
List pgadmin-hackers
On Mon, Mar 7, 2011 at 6:21 AM, Guillaume Lelarge
<guillaume@lelarge.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

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Feature: visual feedback of disabled triggers
Next
From: Dave Page
Date:
Subject: s/xpm/png/g