Skip site navigation (1) Skip section navigation (2)

Re: [SQL] Proposed Changes to PostgreSQL

From: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: chris(at)bitmead(dot)com, pgsql-hackers(at)postgreSQL(dot)org, pgsql-sql(at)postgreSQL(dot)org
Subject: Re: [SQL] Proposed Changes to PostgreSQL
Date: 2000-02-03 04:11:01
Message-ID: 3898FFD5.5D40C507@nimrod.itg.telecom.com.au (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-sql
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.

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2000-02-03 04:22:05
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Previous:From: Bruce MomjianDate: 2000-02-03 04:03:14
Subject: Re: [GENERAL] Proposed Changes to PostgreSQL

pgsql-sql by date

Next:From: Scott ChapmanDate: 2000-02-03 04:15:33
Subject: SQL Query help needed
Previous:From: Bruce MomjianDate: 2000-02-03 04:03:14
Subject: Re: [GENERAL] Proposed Changes to PostgreSQL

pgsql-general by date

Next:From: Bruce MomjianDate: 2000-02-03 04:22:05
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Previous:From: Bruce MomjianDate: 2000-02-03 04:03:14
Subject: Re: [GENERAL] Proposed Changes to PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group