Re: Regarding GSoc 2012 project idea

Hello, Dave
cc: Atri

Hmm... Out of items in "1. Missing features of JDBC specification(big
features)", I wonder if the following ones might be the candidates, though
I'm not confident:

Statement pooling
Ability to identify parameters to CallableStatement objects by name as well
as by index
Enhanced Blob/Clob functionality -- Support provided to create and free a
Blob/Clob instance as well as additional methods added to improve
accessiblity (e.g. Connection interface's createBlob()/createClob())
Availability to be notfied when a PreparedStatement that is associated with
a PooledConnection has been closed or the driver determines is invalid
Setting and getting of client information for connections: Connection
interface's setClientInfo()/getClientInfo()

But as you said "realistically," they may be difficult to implement only in
a summer...I'm wondering what would be beneficial to many users and
relatively addressable.

The core question I'd like to know the answer for is "what should be done
for JDBC driver to make many PostgreSQL users happier and attract more
people to PostgreSQL?". With that eye, I thought it would be interesting to
add supported JDBC features so that more software can interoperate with
PostgreSQL. However, I don't know which JDBC features will be effective to
widen PostgreSQL ecosystem. That investigation itself is a valuable topic,
isn't it?

Regards
MauMau