Thread: tables (and other objects) are automatically put into a schema named"public"
tables (and other objects) are automatically put into a schema named"public"
From
PG Doc comments form
Date:
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.6/ddl-schemas.html Description: This statement is not true and is contradicted in https://www.postgresql.org/docs/9.6/sql-createtable.html which states correctly that: If a schema name is given (for example, CREATE TABLE myschema.mytable ...) then the table is created in the specified schema. Otherwise it is created in the current schema. It is also worth mentioning that if current_schema is empty (i.e. ,search_path is empty or contains the names of non-existent schemas) you get the error: ERROR: no schema has been selected to create in
Re: tables (and other objects) are automatically put into a schemanamed "public"
From
Peter Eisentraut
Date:
On 08/11/2018 21:32, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/ddl-schemas.html > Description: > > This statement is not true and is contradicted in > https://www.postgresql.org/docs/9.6/sql-createtable.html which states > correctly that: > If a schema name is given (for example, CREATE TABLE myschema.mytable ...) > then the table is created in the specified schema. Otherwise it is created > in the current schema. The statement refers to the previous examples and says "by default". I don't think the statement is incorrect or inappropriate. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services