From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200303220153.h2M1r9X01499@candle.pha.pa.us>
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
In-Reply-To: <3E7BA003.9070501@xythos.com>
To: Barry Lind <blind@xythos.com>
Date: Fri, 21 Mar 2003 20:53:09 -0500 (EST)
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>,
	Alvaro Herrera <alvherre@dcc.uchile.cl>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Barry Lind wrote:
> 
> 
> Bruce Momjian wrote:
> > I was thinking if we had a SET PERMANENT that couldn't be changed,
> > interfaces that want to control variables could set them perminantly,
> > and others could let users control it.
> 
> SET PERMANENT only works for those variables that can only have one 
> value for a given client protocol (for example datestyle in jdbc). 
> Whereas autocommit needs to be changeable by the jdbc driver since the 
> jdbc spec allows the user to call an API method to change the setting.

Oh, good point.

> 
> > 
> > Actually, if we reported change to the client, the interface could
> > override any change the user made --- just an idea.
> 
> Reporting the change to the client seems sufficient for the client to 
> take whatever actions are necessary.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073