Re: CREATE SCHEMA IF NOT EXISTS
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: "David E. Wheeler" <david@justatheory.com>, "Dickson S. Guedes" <listas@guedesoft.net>, fabriziomello <fabriziomello@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-10-02T19:48:33Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > Excerpts from David E. Wheeler's message of mar oct 02 16:16:37 -0300 2012: >> On Oct 2, 2012, at 12:08 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: >>> create schema if not exists foo create table first (a int); >>> create schema if not exists foo create table second (a int); >>> >>> As far as I can see, with the patch as it currently stands, you would >>> end up with only table "first" in the schema, which seems very >>> surprising to me. >> Yeah, I think the second should die. CINE should only work if there are no other objects created as part of the statement, IMHO. > Well, if that's the rationale then you end up with no schema foo at all > (i.e. both die), which seems even more surprising (though I admit it has > the advantage of being a simple rule to document.) I think we should just disallow putting any contained objects in the statement when IF NOT EXISTS is used. It's simple to understand, simple to document and implement, and I think it covers all the sane use-cases anyway. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Document the lack of reading the PGDATABASE environment variable in
- 483c2c1071c4 9.3.0 cited