|
Daniel John Debrunner wrote: I agree. I guess what i was trying to say is that I assume that the bulk of the new client driver is a stripped down version of the IBM DB2 driver so that if you could run the test side by side using both drivers and are able to compare the source, it might be easier to figure out where the disconnect is based on the port of the code.Lance J. Andersen wrote:I have had a report internally where we have 2 unit tests fail with the DerbyNetwork client driver that did not fail with the DB2 type 4 driver with Derby. If that is not possible, there is always the old fashioned way ;-) I am waiting on this from the QA team as it is part of a pretty big test harness. Once I have this, i will enter a jira.Let's see what the issue is once you have a reproducible case. Dan. |
- Re: Planning for a 10.1 release Lance J. Andersen
- Re: Planning for a 10.1 release Kathey Marsden
- Re: Planning for a 10.1 release Jeremy Boynes
- Re: Planning for a 10.1 release Kathey Marsden
- Re: Planning for a 10.1 release David Jencks
- Re: Planning for a 10.1 releas... Daniel John Debrunner
- Re: Planning for a 10.1 re... Jeremy Boynes
- Re: Planning for a 10.... Daniel John Debrunner
- Re: Planning for a 10.... Jeremy Boynes
- Re: Planning for a 10.... Satheesh Bandaram
- Re: Planning for a 10.... Jeremy Boynes
