Allow CREATE TABLE IF EXIST so succeed if the schema is nonexistent
Previously, CREATE TABLE IF EXIST threw an error if the schema was
nonexistent. This was done by passing 'missing_ok' to the function that
looks up the schema oid.
Branch
--
master
Details
---
http://git.postgresql.org/
On Sat, Jan 26, 2013 at 1:24 PM, Bruce Momjian wrote:
> Allow CREATE TABLE IF EXIST so succeed if the schema is nonexistent
>
you meant DROP TABLE IF EXISTS, right?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Ce
Issue ERROR if FREEZE mode can't be honored by COPY
Previously non-honored FREEZE mode was ignored. This also issues an
appropriate error message based on the cause of the failure, per
suggestion from Tom. Additional regression test case added.
Branch
--
master
Details
---
http://git.p
On Sat, Jan 26, 2013 at 01:30:53PM -0500, Jaime Casanova wrote:
> On Sat, Jan 26, 2013 at 1:24 PM, Bruce Momjian wrote:
> > Allow CREATE TABLE IF EXIST so succeed if the schema is nonexistent
> >
>
> you meant DROP TABLE IF EXISTS, right?
Oh, yes. DROP TABLE. I needed to update some C comments
Update LookupExplicitNamespace() comments; commit message update
Also, commit 7e2322dff30c04d90c0602d2b5ae24b4881db88b affected DROP
TABLE IF EXISTS, not CREATE TABLE IF EXISTS.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/51cfb87ae235ffc875946bcb6cb8404fe97cbb9b
Update comments in new DROP IF EXISTS code; commit message update
DROP IF EXISTS with a missing schema in commit
7e2322dff30c04d90c0602d2b5ae24b4881db88b applies not only to tables, but
to DROP IF EXISTS with missing schemas for indexes, views, sequences,
and foreign tables. Yeah!
Branch
--
Make LATERAL implicit for functions in FROM.
The SQL standard does not have general functions-in-FROM, but it does
allow UNNEST() there (see the production),
and the semantics of that are defined to include lateral references.
So spec compliance requires allowing lateral references within UNNEST(
