On Fri, Feb 11, 2011 at 5:11 PM, Nikhil S <nixmisc(at)gmail(dot)com> wrote:
>> > Note that if there are no default values, the the defvals column is
>> > completely empty. Now why we see the "" for non-default arguments - the
>> > issue seems to be on the server side in the contrib module calls to
>> > compute
>> > the default values.
>> We need to change that then - we can't have the missing default values
>> default to something that's not valid for that datatype. Change them
>> to null or just empty them?
> Hmmm, well variables can default to NULL too. The backend code tries to
> track those variables which default to NULL or to other values. For the
> rest, it defaults them to "". It then uses construct_md_array to generate
> the output string for type TEXTOID. Dunno if we can have nothing (an empty
> string) as valid TEXTOID output. I guess it's a limitation for this type.
> Let me see if we can do something here on the backend side...
Doesn't really help, as we need to ensure it works sanely with
existing servers too.
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
In response to
pgadmin-hackers by date
|Next:||From: Dave Page||Date: 2011-02-11 16:56:09|
|Subject: Re: phase 2 of wxWidgets 2.9 build|
|Previous:||From: Nikhil S||Date: 2011-02-11 16:11:33|
|Subject: Re: pgAdmin III: the debugger does not pre-populate
default values for arguments|