Re: JDBC 4 support - Mailing list pgsql-jdbc

So first hurdle:

Caused by: org.postgresql.util.PSQLException: Method
org.postgresql.jdbc4.Jdbc4Connection.createBlob() is not yet
implemented.

Same for createClob and createNClob

On Fri, 2009-09-25 at 10:56 -0500, Steve Ebersole wrote:
> Internally Hibernate needs very little.
>
> I'd like to take advantage of Connection#createBlob,
> Connection#createClob and Connection#createNClob (we do not really offer
> built in support for the new SQLXML type, so we wont be binding to
> Connection#createSQLXML(), etc, though of course users might want to as
> an extension).
>
> I'd like to be able to leverage the new exception hierarchy.
>
> For everything else, its really just a curiosity about what the user can
> reasonably expect in terms of portability.
>
>
> On Fri, 2009-09-25 at 11:37 -0400, Dave Cramer wrote:
> > So what functionality of JDBC4 do you need/want for hibernate ?
> >
> > Dave
> >
> > On Fri, Sep 25, 2009 at 11:15 AM, Steve Ebersole <steve@hibernate.org>
> > wrote:
> >         Thanks for the reply.  Its more of a general question.
> >
> >         I am looking at adding JDBC4 (JDK1.6) support to Hibernate.
> >          So the
> >         question came up about whether to drop JDBC3 support or
> >         whether to
> >         support both JDBC3 and JDBC4 simultaneously.  Moving to JDBC4
> >         exclusively is largely a function of how well we thought
> >         JDBC4/JDK1.6 is
> >         supported both in the various environments as well by the
> >         various JDBC
> >         drivers.
> >
> >         Sun's JDK 1.5 is nearing the end of its EOL transition and set
> >         to reach
> >         ESOL Oct 31.  So in the ideal world (since the release I am
> >         targeting
> >         here is November) we would simply drop support for it...
> >
> >
> >         On Fri, 2009-09-25 at 10:07 -0400, Kris Jurka wrote:
> >         >
> >         > On Wed, 23 Sep 2009, Steve Ebersole wrote:
> >         >
> >         > > The download page[1] still lists JDBC 4 support as
> >         "limited" saying that
> >         > > "the majority of new methods are stubbed out".  Is that
> >         really still the
> >         > > case?  How far off is complete JDBC 4 support?
> >         > >
> >         >
> >         > Tough to say without going through each JDBC 4 feature.  The
> >         note you
> >         > mention is certainly old, but there are still significant
> >         JDBC4
> >         > requirements that haven't been implemented (Wrapper support,
> >         specific
> >         > exceptions, ...).
> >         >
> >         > Is there anything in particular that you're interested in?
> >         >
> >         > Kris Jurka
> >         --
> >
> >         Steve Ebersole <steve@hibernate.org>
> >         Hibernate.org
> >
> >
> >         --
> >
> >
> >         Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> >         To make changes to your subscription:
> >         http://www.postgresql.org/mailpref/pgsql-jdbc
> >
> >
--
Steve Ebersole <steve@hibernate.org>
Hibernate.org