Re: [pgadmin-hackers] SET search_path = value

2010-04-21 Thread Guillaume Lelarge
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

Re: [pgadmin-hackers] SET search_path = value

2010-04-20 Thread Guillaume Lelarge
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 e

Re: [pgadmin-hackers] SET search_path = value

2010-04-19 Thread Guillaume Lelarge
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 >> a

Re: [pgadmin-hackers] SET search_path = value

2010-04-19 Thread Euler Taveira de Oliveira
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.

Re: [pgadmin-hackers] SET search_path = value

2010-04-19 Thread Guillaume Lelarge
Le 19/04/2010 04:43, Erwin Brandstetter a écrit : > Hi developers! > > Just created a ticket concerning a minor error in the reverse engineered > SQL code for roles > > Besides the example ... > ALTER ROLE SET search_path = test, public; > --> ALTER DATABASE test SET search_path='test, public

[pgadmin-hackers] SET search_path = value

2010-04-19 Thread Erwin Brandstetter
Hi developers! Just created a ticket concerning a minor error in the reverse engineered SQL code for roles Besides the example ... ALTER ROLE SET search_path = test, public; --> ALTER DATABASE test SET search_path='test, public';-- quotes are wrong ... there are at least two more occ