Why Use Multiple Schemas?

I mentioned that Postgres supports multiple clusters, databases, and
schemas, but an open question is why use multiple schemas, rather than placing everything in the "public" schema? By default,
search_path places everything
in the public schema (assuming a schema matching the current user name does not exist):

test=> SHOW search_path;
  search_path
----------------
 "$user",public
(1 row)

Continue Reading »

Why Use Multiple Schemas?
By  , Apr 27, 2012

I mentioned that Postgres supports multiple clusters, databases, and
schemas, but an open question is why use multiple schemas, rather than placing everything in the "public" schema? By default,
search_path places everything
in the public schema (assuming a schema matching the current user name does not exist):

test=> SHOW search_path;
  search_path
----------------
 "$user",public
(1 row)

Continue Reading »

Tags:
mailto:?subject= Why Use Multiple Schemas? &body= Why Use Multiple Schemas? %20:%20http://www.enterprisedb.com/why-use-multiple-schemas