Re: JDBC 2.0 conformance, documentation and todo list - Mailing list pgsql-jdbc
From | Barry Lind |
---|---|
Subject | Re: JDBC 2.0 conformance, documentation and todo list |
Date | |
Msg-id | 3B7209D5.7050305@xythos.com Whole thread Raw |
In response to | JDBC 2.0 conformance, documentation and todo list (Rene Pijlman <rpijlman@wanadoo.nl>) |
Responses |
Re: Re: JDBC 2.0 conformance, documentation and todo list
Re: Re: JDBC 2.0 conformance, documentation and todo list |
List | pgsql-jdbc |
Rene, First off, thank you for pulling this information together in one place. It is really appreciated. I was going through your list of issues and I had the following comments to add: Batch Updates The current implementation is poor. As you point out the implementation of storing up the statements and then executing them one by one defeats the purpose of the batch methods. The intended behaviour is to send a set of updates/inserts in one round trip to the database. The server does support this functionality (you can send multiple statements in one call by using a semicolon as a statement separator). The server will then execute them all at once. The one limitation is that the oid/row count returned by such a batch update only reflects the oid/row count of the last statement in the batch. In reading the spec this behaviour is in conformance if not ideal. DatabaseMetaData getDatabaseProductVersion - I get a pass on this test when I run. supportsANSI92EntryLevelSQL - Since postgres now does support outer joins, I think the answer here should be yes. I think the general feeling is that if there is a deviation from entry level SQL92 it is a bug. PreparedStatement The bytea type is documented for 7.2. You can see it in the current docs off of the developers corner links. The driver does implement setBlob the same way as setBinaryStream. In fact it uses setBinaryStream in it's implementation. I believe that setBlob is functionally correct in it's assumptions that the underlying type is oid and thus a LargeObject. General Requirements ODBC escape processing is minimally handled. The escapes for date format are supported, but not the rest. thanks, --Barry Rene Pijlman wrote: > Hello, > > I've created a web page that aims to document the level of > conformance of the JDBC driver to the JDBC 2.0 API. It also aims > to document any deviations from the JDBC standard that have been > found. > http://lab.applinet.nl/postgresql-jdbc/ > > No need to say its still far from complete. I just wrote the > sections on Array and Batch Updates. I'm volunteering to finish > and maintain this page if people find it useful. Any comments? > > Any feedback or additions will be greatly appreciated. If you > know about a JDBC 2.0 feature that seems to be missing or a > feature you know is implemented, please post a message on this > list. > > The reason I created this page is that I wanted to work on JDBC > 2.0 conformance, and except for Blob/Clob support Barry Lind > wrote about a couple of days ago, it wasn't clear what needed to > be done. Investigating and documenting the conformance level and > known deficiencies seemed like a good place to start. > > Regards, > René Pijlman > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > >
pgsql-jdbc by date: