Sender: arkin@arkin.exoffice.com
Message-ID: <389F3988.B5189904@exoffice.com>
Date: Mon, 07 Feb 2000 13:30:48 -0800
From: Assaf Arkin <arkin@exoffice.com>
Organization: Exoffice
MIME-Version: 1.0
To: Peter Mount <petermount@it.maidstone.gov.uk>
CC: "'Joe Shevland'" <shevlandj@kpi.com.au>,
	"'Jaume Pausas'" <a1649@dis.ulpgc.es>, pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] ConnectionPoolDataSource (JDBC)
References: 
 <1B3D5E532D18D311861A00600865478C70C16B@exchange1.nt.maidstone.gov.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Peter Mount wrote:
> 
> New in the 7.0 driver:
> * javax.sql support (thanks arkin)

Thank you. I want to point out that the Oracle JDBC drivers do not seem
to support javax.sql yet. Nice to see Postgresql getting ahead of the
curve :-)

Are there any plans to support X/Open error code reporting? Rather than
just reporting the message, the X/Open error code will be reported
allowing the application to determine from the SQLException what went
wrong. This allows the application to determine duplicate keys, aborted
transactions, etc.


> * ResultSet to use a cursor when retrieving results

Which type of cursors will be supported?

arkin

> These won't be done until after 7.0:
> * RowSet's
> * Updateable ResultSet's (not sure how to do this yet)
> 
> Peter

-- 
----------------------------------------------------------------------
Assaf Arkin                                           www.exoffice.com
CTO, Exoffice Technologies, Inc.                        www.exolab.org