Обсуждение: Objects without schema
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/9.5/ddl-schemas.html Description: In the last section of the document it says 'If you need to work with those systems, then maximum portability would be achieved by not using schemas at all.'. But how do we achieve this? If I am not mistaken, all objects(like tables) created in the database need to be created under one schema. Thanks, Joby
On 11/30/2018 02:27 AM, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.5/ddl-schemas.html > Description: > > In the last section of the document it says 'If you need to work with those > systems, then maximum portability would be achieved by not using schemas at > all.'. > But how do we achieve this? If I am not mistaken, all objects(like tables) > created in the database need to be created under one schema. Correct, in that every object has to have a schema, by default the "public" schema. I suspect what this is trying to say is that you should keep all objects under one schema, and not explicitly reference that schema; that way queries and DDL would be more portable. Regards Ian Barwick -- Ian Barwick http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Ok. Thank you for the clarification.
On Fri, 30 Nov 2018 at 01:44, Ian Barwick <ian.barwick@2ndquadrant.com> wrote:
On 11/30/2018 02:27 AM, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.5/ddl-schemas.html
> Description:
>
> In the last section of the document it says 'If you need to work with those
> systems, then maximum portability would be achieved by not using schemas at
> all.'.
> But how do we achieve this? If I am not mistaken, all objects(like tables)
> created in the database need to be created under one schema.
Correct, in that every object has to have a schema, by default the "public"
schema.
I suspect what this is trying to say is that you should keep all objects under
one schema, and not explicitly reference that schema; that way queries and DDL
would be more portable.
Regards
Ian Barwick
--
Ian Barwick http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services