pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedObjects without schema
3+ messages / 3 participants
[nested] [flat]
* Objects without schema
@ 2018-11-29 17:27 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2018-11-29 17:27 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: jobyjc@gmail.com
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Objects without schema
@ 2018-11-30 01:44 Ian Barwick <ian.barwick@2ndquadrant.com>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 3+ messages in thread
From: Ian Barwick @ 2018-11-30 01:44 UTC (permalink / raw)
To: jobyjc@gmail.com, pgsql-docs@lists.postgresql.org, PG Doc comments form <noreply@postgresql.org>
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Objects without schema
@ 2018-11-30 21:14 Joby John <jobyjc@gmail.com>
parent: Ian Barwick <ian.barwick@2ndquadrant.com>
0 siblings, 0 replies; 3+ messages in thread
From: Joby John @ 2018-11-30 21:14 UTC (permalink / raw)
To: ian.barwick@2ndquadrant.com; +Cc: pgsql-docs@lists.postgresql.org; noreply@postgresql.org
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
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2018-11-30 21:14 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-11-29 17:27 Objects without schema PG Doc comments form <noreply@postgresql.org>
2018-11-30 01:44 ` Ian Barwick <ian.barwick@2ndquadrant.com>
2018-11-30 21:14 ` Joby John <jobyjc@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox