Oracle JDBC version - 11gR2 version should be used instead of 10g about dbfit HOT 11 CLOSED

Thanks for the feedback, I shall bump the oracle version used in development to the latest. It's just a legacy of reviving a project that hasn't really been updated for 3 years :)

As it stands, I am not aware of anything that should prevent you from using 11.2 for your test setup; should something arise, please raise it here as a bug.

from dbfit.

Just tested my old project with dbfit 2.0RC3 + jdbc 11.2.0.3 - all seems OK.

from dbfit.

Cool, thanks!

On 6 Mar 2013, at 21:06, javornikolov [email protected] wrote:

Just tested my old project with dbfit 2.0RC3 + jdbc 11.2.0.3 - all seems OK.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/28#issuecomment-14526092
.

from dbfit.

I just faced an issue with that when using NCLOB column (same works fine with the old 10g ojdbc14.jar). This sounds like #14 is incompatible with the 11gR2 driver.

Query   select name, value from crap2
name    value
name missing    Batman
name surplus    oracle.sql.NCLOB@74178802

from dbfit.

The NCLOB issue is something I may try to handle in a pull request when I find some time. (Seems simple enough for something to start with :-))

from dbfit.

Ah, perfect...

from dbfit.

I would like to maintain 10g compatibility somehow, if possible, but have no real way to test against a 10g database. I can't see 10g XE available anywhere.

Does it make sense to run two builds:

1. One with the 10g driver against 11g
2. One with the 11g driver against 11g?

does 1. even make sense?

from dbfit.

11gR2 driver should work fine against 10g database too.

from dbfit.

11gR2 driver should work fine against 10g database too.

do we know this for sure? is there a way to test this?

from dbfit.

Yes, we know this (this is the official statement). But I haven't tested with dbfit but I certainly used other JDBC tools in past.

No live 10g around me (I upgraded them all). But I can try to setup a 10g instance and run some tests on top of it.

So officially - both 11.2 and 10.2 are certified to work with following db versions: 11.2.0, 11.1.0, 10.2.0, 10.1.0, 9.2.0.

However in forward direction - some features may not work. E.g. - there are new security recommendations in 11g which if enabled authentication with 10g thin driver won't work.

In addition - official information is like that:

• 10.2 ojdbc4.jar is compatible with JDK 1.4 and 1.5. (We're building with 1.6. It works fine but it's not officially certified). There are also drivers for 1.2 and 1.3 but these are not so interesting.
• 11.2.0.3 ojdbc6.jar v - compatible with JDK 1.6, 1.7. ojdbc5.jar - with JDK 1.5

In general 10g db is going out of support (few more months and even extended support is ending).

Here is my suggestion:

• I'll try to make it work with both 10g and 11.2.0.3 drivers. (E.g. - using the parent class lookup and/or the String approach).
• I'll also bump up driver version to 11.2.0.3 so it's the default.

So there will be transitional period when even though 11.2 driver is default: If someone has a problem - should be able to swap it back to other version; and will report the problem. If no problems for a while - in next release we can afford to make some changes which possibly break 10g compatibility.

from dbfit.

Thanks for the thorough reply.

Yes, we know this (this is the official statement). But I haven't tested
with dbfit but I certainly used other JDBC tools in past.

No live 10g around me (I upgraded them all). But I can try to setup a 10g
instance and run some tests on top of it.

If you don't have a 10g instance to hand, don't bother. That time would be
better spent on other stuff. Older versions of DbFit will still be there,
and we could easily patch any problems.

So officially - both 11.2 and 10.2 are certified to work with following db
versions: 11.2.0, 11.1.0, 10.2.0, 10.1.0, 9.2.0.

However in forward direction - some features may not work. E.g. - there are
new security recommendations in 11g which if enabled authentication with
10g thin driver won't work.

In addition - official information is like that:

• 10.2 ojdbc4.jar is compatible with JDK 1.4 and 1.5. (We're building
  with 1.6. It works fine but it's not officially certified). There are also
  drivers for 1.2 and 1.3 but these are not so interesting.
• 11.2.0.3 ojdbc6.jar v - compatible with JDK 1.6, 1.7. ojdbc5.jar -
  with JDK 1.5

In general 10g db is going out of support (few more months and even
extended support is ending).

Here is my suggestion:

• I'll try to make it work with both 10g and 11.2.0.3 drivers. (E.g. -
  using the parent class lookup and/or the String approach).
• I'll also bump up driver version to 11.2.0.3 so it's the default.

Sounds good.

from dbfit.