From: | Assaf Arkin <arkin(at)exoffice(dot)com> |
---|---|
To: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
Cc: | "'Joe Shevland'" <shevlandj(at)kpi(dot)com(dot)au>, "'Jaume Pausas'" <a1649(at)dis(dot)ulpgc(dot)es>, pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] ConnectionPoolDataSource (JDBC) |
Date: | 2000-02-07 21:30:48 |
Message-ID: | 389F3988.B5189904@exoffice.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Axel at ansonic | 2000-02-08 01:47:22 | RE: [INTERFACES] Bug in parser? |
Previous Message | Christian Schaer | 2000-02-07 20:25:11 | Approach can't open ... |