Skip site navigation (1) Skip section navigation (2)

Re: pgAdmin III: the debugger does not pre-populate default values for arguments

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-10 15:18:51
Message-ID: AANLkTimGCRJ8fm_ycCSBm4stOX_NpJuqtzoCaXKjy9Ek@mail.gmail.com (view raw or flat)
Thread:
Lists: pgadmin-hackers
On Mon, Feb 7, 2011 at 9:03 AM, Nikhil S <nixmisc(at)gmail(dot)com> wrote:
> One side-effect of this feature is that earlier where non-default variables
> appeared as empty, they will now appear with values "". This will happen
> only if some arguments have defvals and some don't. We could have added code
> to do away with "" entries, but then I thought it is possible for people to
> provide "" as default values too. So we can live with this I think..
>

Even for non-strings?

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2011-02-10 21:51:37
Subject: pgAdmin III commit: Fix the collate and ctype combobox on dlgDatabase
Previous:From: Nikhil SDate: 2011-02-10 14:29:03
Subject: Re: pgAdmin III: error while browsing schema of PG database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group