db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.
Date Wed, 16 Nov 2005 18:56:17 GMT
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.


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.

View raw message