From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #169: SET search_path = value |
Date: | 2010-04-19 01:50:36 |
Message-ID: | 045.3aa022c7e15b9aa4d062a99cadd09380@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#169: SET search_path = value
-----------------------------+----------------------------------------------
Reporter: brsa | Owner: dpage
Type: bug | Status: new
Priority: critical | Milestone:
Component: pgadmin | Version: 1.10
Keywords: browser sqlpane | Platform: all
-----------------------------+----------------------------------------------
The syntax for the SQL command SET requires a value, not a string (with
single quotes) in a number of cases. Not exactly intuitive but that's how
it is.
The reverse engineered code for roles falls victim to this pitfall and
adds single quotes, which is wrong.
-- demo --
-- I say:
CREATE ROLE test;
ALTER ROLE test SET search_path=test, public;
-- pgAdmin says:
CREATE ROLE test
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
ALTER ROLE test SET search_path='test, public'; -- note the quotes!
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/169>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2010-04-19 01:57:56 | Re: [pgAdmin III] #169: SET search_path = value |
Previous Message | Guillaume Lelarge | 2010-04-17 18:09:27 | Re: Ticket 3: groups of servers |