Horton
Menu

Re: CREATE SCHEMA IF NOT EXISTS

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, 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-02T20:38:20Z
Lists: pgsql-hackers 
Excerpts from Andrew Dunstan's message of mar oct 02 17:24:38 -0300 2012:
> 
> On 10/02/2012 03:48 PM, Tom Lane wrote:
> > Alvaro Herrera <alvherre@2ndquadrant.com> writes:

> >> 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.
> 
> I thought we'd already agreed on this.

Well, it's not what the latest proposed patch implements.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Document the lack of reading the PGDATABASE environment variable in