Re: Unhappy thoughts about pg_dump and objects inherited from template1

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unhappy thoughts about pg_dump and objects inherited from template1
Date: 2000-11-08 16:11:17
Message-ID: 20001108101117.B15454@rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 09, 2000 at 02:48:50AM +1100, Philip Warner wrote:
> At 10:15 8/11/00 -0500, Tom Lane wrote:
> >I like
> >
> > CREATE DATABASE foo WITH TEMPLATE 'template0'
> >
> >better than a SET command.
>
> Just seems like we'd be forcing non-standard syntax on ourselves when/if
> CREATE DATABASE becomes CREATE SCHEMA; I would assume that the two
> statements would become synonymous? Since this code is only for pg_dump,
> polluting CREATE DATABASE even further seems like a bad idea. No big deal,
> though.

Nope, we'll still have databases, with schema inside them. Schema are
essentially a logical namespace, while a database encompasses all the data
objects accessible to one session (via standard SQL), i.e. one backend.

As Tom said, creating and maintaining those are 'implementation defined'
in the standard.

Ross
--
Open source code is like a natural resource, it's the result of providing
food and sunshine to programmers, and then staying out of their way.
[...] [It] is not going away because it has utility for both the developers
and users independent of economic motivations. Jim Flynn, Sunnyvale, Calif.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-08 16:13:46 Re: Unhappy thoughts about pg_dump and objects inherited from template1
Previous Message Ross J. Reedstrom 2000-11-08 16:07:44 Re: AW: Re: [GENERAL] Query caching