Re: [HACKERS] Schemas: status report, call for developers - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: [HACKERS] Schemas: status report, call for developers
Date
Msg-id 11633.1023512009@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Schemas: status report, call for developers  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] Schemas: status report, call for developers  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-interfaces
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I am a little uncomfortable about this.  It means that CREATE TABLE will
> create a table in 'public' if the user doesn't have a schema of their
> own, and in their private schema if it exists.  I seems strange to have
> such a distinction based on whether a private schema exists.  Is this OK?

You have a better idea?

Given that we want to support both backwards-compatible and SQL-spec-
compatible behavior, I think some such ugliness is inevitable.
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Schemas: status report, call for developers
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Schemas: status report, call for developers