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

The trouble with search_path ...

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: The trouble with search_path ...
Date: 2004-06-10 18:20:57
Message-ID: 20040610182057.21913.qmail@web13807.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgadmin-hackers
Please try to reproduce this bug:

Select properties on a database element. 
Click to the Variables tab
Select "search_path" from the drop-down
Set the Variable value textfield to "public, pgcatalog, my_schema"
Click OK.

in the description pane you'll find:

-- Database: data

-- DROP DATABASE data;

CREATE DATABASE data
  WITH ENCODING = 'SQL_ASCII';
ALTER DATABASE data SET "search_path=public,;
ALTER DATABASE data SET pg_catalog,;
ALTER DATABASE data SET my_schema";

Somehow I don't think that's the right syntax... Since I've done this, how can
I undo it?

ALTER DATABASE RESET "search_path=public,;
ALTER DATABASE data SET pg_catalog,;
ALTER DATABASE data SET my_schema";

?

CG


	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/ 

Responses

pgadmin-hackers by date

Next:From: Andreas PflugDate: 2004-06-10 20:22:56
Subject: Re: The trouble with search_path ...
Previous:From: Adam H. PendletonDate: 2004-06-10 18:07:42
Subject: Re: pgAdmin3 doesn't work after upgrading FC1 to

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