Re: SET search_path = value - Mailing list pgadmin-hackers

From Guillaume Lelarge
Subject Re: SET search_path = value
Date
Msg-id 4BCF701C.6000706@lelarge.info
Whole thread Raw
In response to Re: SET search_path = value  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-hackers
Le 21/04/2010 00:24, Guillaume Lelarge a écrit :
> Le 20/04/2010 08:54, Guillaume Lelarge a écrit :
>> Le 20/04/2010 05:28, Euler Taveira de Oliveira a écrit :
>>> Guillaume Lelarge escreveu:
>>>> pgAdmin shouldn't use quotes on some parameters: search_path,
>>>> temp_tablespaces. Perhaps others. I don't find a way to pick them
>>>> automatically. For example, their vartype are "string". Which is quite
>>>> ambiguous with others "string" parameters like archive_command. Of
>>>> course, we can use a specific code for them. It would be really easy,
>>>> but I would prefer to find another way.
>>>>
>>> I don't see an easy way. :( Perhaps the plan could be map all of these
>>> parameters (because in the future legacy versions will use this code path) and
>>> then implement a way to identify those strings without quotes in PostgreSQL.
>>
>> Yeah, I don't find a better way to fix this right now.
>>
>
> Fix commited for 1.10. Still needs to work on the trunk patch. Will do
> tomorrow.
>

Fixed in trunk too, with another issue.


--
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com

pgadmin-hackers by date:

Previous
From: "pgAdmin Trac"
Date:
Subject: Re: [pgAdmin III] #169: SET search_path = value
Next
From: svn@pgadmin.org
Date:
Subject: SVN Commit by dpage: r8291 - trunk/pgadmin3/pgadmin/include