Re: [SQL] Proposed Changes to PostgreSQL - Mailing list pgsql-hackers

From Chris Bitmead
Subject Re: [SQL] Proposed Changes to PostgreSQL
Date
Msg-id 3898FFD5.5D40C507@nimrod.itg.telecom.com.au
Whole thread Raw
In response to Proposed Changes to PostgreSQL  (Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>)
Responses Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> Again, I think you've got the default backwards.  I remind you also
> of something we've been beating on Peter about: psql is an application
> scripting tool, so you don't get to redefine its behavior at whim,
> anymore than you can change libpq's API at whim.

If this is the only objection, we could make the old behaviour available
by a SET command, as well as a command-line switch, as well as a 
./configure option.

I hope we can get the best design here possible without over-emphasis
on compatibility.


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [SQL] Proposed Changes to PostgreSQL
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL