From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Nikhil S <nixmisc(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAdmin III: the debugger does not pre-populate default values for arguments |
Date: | 2011-02-12 06:45:11 |
Message-ID: | AANLkTi=pyxVbBYfjtCnCWvMkxr4Wx0diCmC7BQkT3+Z5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Sat, Feb 12, 2011 at 6:32 AM, Nikhil S <nixmisc(at)gmail(dot)com> wrote:
>
>> > 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.
>>
>
> Well it will work with only those servers which support default values for
> arguments (PG 8.4 onwards, right?).
>
> But I guess you mean, we should find a solution more on the pgadmin side
> instead of tinkering with the backend?
Yes.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2011-02-12 08:20:41 | pgAdmin III commit: make style once again forgotten |
Previous Message | Nikhil S | 2011-02-12 05:32:14 | Re: pgAdmin III: the debugger does not pre-populate default values for arguments |