For those that are curious. I ran the hibernate 2.1.2 test suite with the development jTDS driver(checked in code as of 2004-02-14) and only 11 tests failed. For comparision, the released 0.6 driver failed 63 tests. The hibernate 2.1.2 test suite contains over 200 test.
(I do not use hibernate myself, but I wanted to see how compatbile the driver is and where any problems may exist)
-Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is great! I did the same thing more than a year ago with the JDBC certification test suite and it helped me fix a number of issues I wasn't aware of.
I think that if I manage to pull off updatable ResultSets, then we apply Mike's patch and move to a single connection and finally make scrollable/updatable ResultSets work with prepared and callable statements (even by simulating prepared statements with plain statements, for the beginning) we should be able to pass any set of tests.
Alin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran the test suite with the Microsoft (SP2) driver yesterday and 9 tests failed. I believe the functionality of the jTDS driver is getting very close to that of other drivers.
-Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LOL! I knew the Microsoft driver was bad, but I had no idea it was so bad! ;o)
BTW, after making the change to the properties file (by adding the driver class to the properties) I ran our test suite with the Microsof driver and JSQLConnect. For my surprise, in addition to a lot of tests that were failing because of different handling of update counts from stored procedures, there were some tests that were actually failing when they shouldn't have. So it seems that yes, we do have a good driver. And we're going to have a better one, soon. :o)
Alin.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For those that are curious. I ran the hibernate 2.1.2 test suite with the development jTDS driver(checked in code as of 2004-02-14) and only 11 tests failed. For comparision, the released 0.6 driver failed 63 tests. The hibernate 2.1.2 test suite contains over 200 test.
(I do not use hibernate myself, but I wanted to see how compatbile the driver is and where any problems may exist)
-Brian
Brian,
This is great! I did the same thing more than a year ago with the JDBC certification test suite and it helped me fix a number of issues I wasn't aware of.
I think that if I manage to pull off updatable ResultSets, then we apply Mike's patch and move to a single connection and finally make scrollable/updatable ResultSets work with prepared and callable statements (even by simulating prepared statements with plain statements, for the beginning) we should be able to pass any set of tests.
Alin.
I ran the test suite with the Microsoft (SP2) driver yesterday and 9 tests failed. I believe the functionality of the jTDS driver is getting very close to that of other drivers.
-Brian
LOL! I knew the Microsoft driver was bad, but I had no idea it was so bad! ;o)
BTW, after making the change to the properties file (by adding the driver class to the properties) I ran our test suite with the Microsof driver and JSQLConnect. For my surprise, in addition to a lot of tests that were failing because of different handling of update counts from stored procedures, there were some tests that were actually failing when they shouldn't have. So it seems that yes, we do have a good driver. And we're going to have a better one, soon. :o)
Alin.