Re: Multiple schemas - Mailing list pgsql-general

From Justin
Subject Re: Multiple schemas
Date
Msg-id CALL-XeMts9mLRa+gYzdoeLjfXBzM=29JxUbgCdVFNesoZnyJJw@mail.gmail.com
Whole thread
In response to Re: Multiple schemas  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-general
Hi Rob Stone

I can not create the behavior you are describing. 
I suspect the
 
set search_path to bsmdl,foots,public

has an issue.

I abuse the search path to override PostgreSQL internal functions.   example search_paths I have created.

search_path to overload_functions,pg_catalog,ar,ap,manufacturing,public, 

Keep i mind the session temp space can not be overridden it will always be searched first.

Below is example

test=# CREATE SCHEMA _1;
CREATE SCHEMA
test=# CREATE SCHEMA _2;
CREATE SCHEMA
test=# create table _1.ff(id int);
CREATE TABLE
test=# create table _2.ff(id int);
CREATE TABLE


test=# set search_path to _1,_2;
SET
test=# insert into ff values (1);
INSERT 0 1
test=# select * from _1.ff ;
 id
----
  1
(1 row)

test=# \d ff
                   Table "_1.ff"
 Column |  Type   | Collation | Nullable | Default
--------+---------+-----------+----------+---------
 id     | integer |           |          |


test=# set search_path to _2, _1;
SET
test=# \d ff
                   Table "_2.ff"
 Column |  Type   | Collation | Nullable | Default
--------+---------+-----------+----------+---------
 id     | integer |           |          |

test=# create table _1.aa();
CREATE TABLE
test=# \d aa
                 Table "_1.aa"
 Column | Type | Collation | Nullable | Default
--------+------+-----------+----------+---------

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Multiple schemas
Next
From: Adrian Klaver
Date:
Subject: Re: Multiple schemas