[pgAdmin III] #169: SET search_path = value
От | pgAdmin Trac |
---|---|
Тема | [pgAdmin III] #169: SET search_path = value |
Дата | |
Msg-id | 045.3aa022c7e15b9aa4d062a99cadd09380@code.pgadmin.org обсуждение исходный текст |
Ответы |
Re: [pgAdmin III] #169: SET search_path = value
Re: [pgAdmin III] #169: SET search_path = value Re: [pgAdmin III] #169: SET search_path = value |
Список | 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
В списке pgadmin-hackers по дате отправления: