As usual when replying from here, replies prefixed with PM:
--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.
-----Original Message-----
From: Assaf Arkin [mailto:arkin@exoffice.com]
Sent: Monday, February 07, 2000 9:31 PM
To: Peter Mount
Cc: 'Joe Shevland'; 'Jaume Pausas'; pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] ConnectionPoolDataSource (JDBC)
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 :-)
PM: It is good to see were ahead of them...
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.
PM: It should be relatively easy. All of our SQLException's are now
keyworded to allow the internationalization of the messages, so in
theory we can add the code by way of a lookup on that keyword.
> * ResultSet to use a cursor when retrieving results
Which type of cursors will be supported?
PM: Not sure yet. I'm currently about 3 days behind (from the point
where I wanted to be by today).
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
