Hi Dyre,
I agree that writing the new test under JUnit would be a great idea. It
would be great if your test extended DerbyJUnitTest and if you beefed up
this class with any utility methods you need which you think other test
writers might appreciate. This might be a good time to create a
junitTests/lang/Bugs.java JUnit test where we can all hang test cases
for language bugs.
Thanks,
-Rick
Kathey Marsden wrote:
Dyre Tjeldvoll (JIRA) wrote:
If am supposed to create a regression test for this; is there any chance that I can do that as JUnit test?
Junit sounds great to me. I think Rick set up the framework for running
Junit tests under derbyall and could perhaps offer some quick tips. (I
think this would make a great Wiki page). I became interested in your
fix because we were recently approached by someone teaching a class who
wanted to use Derby but hit this and was ready to switch to another DB
until they found out there was a workaround. Your fix will be very
valuable because even though there is an easy workaround, this bug is
something that perhaps folks are most likely to hit when migrating to
Derby and they might become discouraged by it.
Thanks
Kathey
