Re: JDBC 4 Compliance

As we have all seen Oracle is pushing forward with the releases of Java. I
myself in the last few months have received notices from Oracle of Java 6
no longer supported, updates to fix security issues with Java 7, and now a
push for Java 8. While a majority of developers are I think comfortable
with Java 6 and argued that it has only been out a few years that will not
last given the accelerated hyper release activities of projects. Look at
Firefox.

The issue here I think is the pushing forward of the pgJDBC, it feels like
it's in maintenance mode. pgJDBC is the official supported driver for PostgreSQL
right?

Now though it appears to have at least one fork, if not multiple. What the
project should be trying to do is bring in new developers like Kevin to work
on the existing pgJDBC driver to bring it in to compliance with the new Java
releases.

I don't know how the pgJDBC project is going to accomplish this, but if
someone could indicated to me how Java Version 7, JDBC4-(4)/JDBC4.1-(4.1),
is referenced by in the code I could try to at least resolve this one issue
by reviewing the existing code and Kevin's to create a patch. Perhaps from
this review IS_GENERATEDCOLUMN could be at least defined if not already so.

danap.
Dana M. Proctor
MyJSQLView Project Manager

Dave Cramer wrote:
> Robert,
>
> What are you looking for here. I'm not sure that the protocol provides
> the information to determine if a column is generated. Generated could
> mean many things....
>
> If on the other hand you just want adherence to the spec and adding the
> column in with a "" as undetermined that seems trivial
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
>
> On Sat, Jun 22, 2013 at 10:53 PM, Kevin Wooten <kdubb@me.com
> <mailto:kdubb@me.com>> wrote:
>
>     I cannot speak to when the main driver will add JDBC 4.1 features.
>       I can say that my alternate driver, the project I linked to
>     previously, does adhere to JDBC 4.1 for the features it implements.
>       You may want to try it out and see if it works for you as its only
>     2 glaring JDBC feature omissions are updatable result-sets and  call
>     statements.
>
>     On Jun 22, 2013, at 7:34 PM, REBruchs <REBruchs@cfl.rr.com
>     <mailto:REBruchs@cfl.rr.com>> wrote:
>
>      > Kevin,
>      >
>      > Thanks for pointing that out.
>      > I noticed the same also. You are also probably aware of the
>     recent turmoil
>      > regarding the security problems with Java and Oracle's efforts to
>     push at
>      > least Java 7u21 and preferably Java 7u25 to the masses.
>      >
>      > Oracle has stated that Java 6u45 has been archived and recommends
>     Java 7.
>      >
>      > My original email was not sent as a complaint, but more as an
>     inquiry as to
>      > when the PostgreSQL JDBC4 driver (that more closely adheres to
>     the Java 7
>      > JDBC API) might be made available to the development community.
>      >
>      > I am a long time PostgreSQL and PostgreSQL JDBC driver user and
>     have been
>      > quite happy with PostgreSQL for quite some time now.
>      >
>      > Thank you for your timely responses, and I applaud your efforts
>     and the
>      > efforts of other JDBC driver team members in continuing to provide
>      > developers of Java/PostgreSQL applications a quality JDBC driver.
>      >
>      > Best regards,
>      >
>      > Robert Bruchs
>      >
>      > -----Original Message-----
>      > From: Kevin Wooten [mailto:kdubb@me.com <mailto:kdubb@me.com>]
>      > Sent: Saturday, June 22, 2013 6:19 PM
>      > To: REBruchs
>      > Cc: 'dmp'; 'PostgreSQL JDBC'
>      > Subject: Re: [JDBC] JDBC 4 Compliance
>      >
>      > Yes. You are referencing the Java 7 documentation which, as I
>     referenced
>      > previously, is JDBC 4.1; the mainstream driver does not currently
>     only
>      > covers JDBC 4.
>      >
>      > If you look at the same Java 6 docs
>      >
>     (http://docs.oracle.com/javase/6/docs/api/java/sql/DatabaseMetaData.html),
>      > which is JDBC 4, you'll see that there is no 24th column.
>      >
>      >
>      > On Jun 22, 2013, at 1:50 PM, REBruchs <REBruchs@cfl.rr.com
>     <mailto:REBruchs@cfl.rr.com>> wrote:
>      >
>      >> Please see the Oracle JAVA SE API documentation at
>      >>
>     http://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html
>      >>
>      >> Refer to method getColumns(), column 24 IS_GENERATEDCOLUMN
>      >>
>      >> Thanks for looking into this.
>      >>
>      >> -----Original Message-----
>      >> From: Kevin Wooten [mailto:kdubb@me.com <mailto:kdubb@me.com>]
>      >> Sent: Saturday, June 22, 2013 2:13 PM
>      >> To: dmp
>      >> Cc: REBruchs; PostgreSQL JDBC
>      >> Subject: Re: [JDBC] JDBC 4 Compliance
>      >>
>      >> This column is defined in JDBC 4.1 which is not supported by the
>     driver.
>      >>
>      >> It is supported in my separate implementation of the driver.
>     pgjdbc-ng
>      >> <https://github.com/kdubb/pgjdbc-ng>
>      >>
>      >>
>      >> On Jun 22, 2013, at 9:49 AM, dmp <danap@ttc-cmc.net
>     <mailto:danap@ttc-cmc.net>> wrote:
>      >>
>      >>
>      >>      It does not appear that method in the Java Docs defines such a
>      >>      column, IS_GENERATEDCOLUMN, to be returned. The code also does
>      >>      not indicated any such column. IS_AUTOINCREMENT maybe? Can you
>      >>      please clarify?
>      >>
>      >>      danap.
>      >>
>      >>      REBruchs wrote:
>      >>
>      >>
>      >>              The 9.2-1002 JDBC 4 driver version does not appear to
>      >> provide the
>      >>              IS_GENERATEDCOLUMN column in the ResultSet returned by
>      >>
>      >>              ResultSet DatabaseMetaData.getColumns(String catalog,
>      >>                                 String schemaPattern,
>      >>                                 String tableNamePattern,
>      >>                                 String columnNamePattern)
>      >>
>      >>
>      >>
>      >>
>      >>
>      >>
>      >>
>      >>      --
>      >>      Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org
>     <mailto:pgsql-jdbc@postgresql.org>)
>      >>      To make changes to your subscription:
>      >> http://www.postgresql.org/mailpref/pgsql-jdbc
>      >>
>      >>
>      >>
>      >>
>      >>
>      >>
>      >> --
>      >> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org
>     <mailto:pgsql-jdbc@postgresql.org>)
>      >> To make changes to your subscription:
>      >> http://www.postgresql.org/mailpref/pgsql-jdbc
>      >
>
>
>
>     --
>     Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org
>     <mailto:pgsql-jdbc@postgresql.org>)
>     To make changes to your subscription:
>     http://www.postgresql.org/mailpref/pgsql-jdbc