Re: JDBC 4 Compliance - Mailing list pgsql-jdbc
From | Kevin Wooten |
---|---|
Subject | Re: JDBC 4 Compliance |
Date | |
Msg-id | 24064BE7-766E-4B4A-923D-C22771D06D35@me.com Whole thread Raw |
In response to | JDBC 4 Compliance ("REBruchs" <REBruchs@cfl.rr.com>) |
Responses |
Re: JDBC 4 Compliance
(Dave Cramer <pg@fastcrypt.com>)
|
List | pgsql-jdbc |
I cannot speak to when the main driver will add JDBC 4.1 features. I can say that my alternate driver, the project I linkedto previously, does adhere to JDBC 4.1 for the features it implements. You may want to try it out and see if it worksfor 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> 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] > 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> 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] >> 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> 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) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-jdbc >> >> >> >> >> >> >> -- >> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-jdbc >
pgsql-jdbc by date: