Re: [jira] Commented: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

[Satheesh Bandaram]

[EMAIL PROTECTED] wrote: "KAH" == Knut Anders Hatlen <[EMAIL PROTECTED]> writes: Hmm, I just discovered, to my surprise and disappointment, that I am unable to test that this actually works, because lang/triggerGeneral.sql does not run under DerbyNet or DerbyNetClient. Why is that? I assumed, in my naivete, that tests should run in all three frameworks, unless the test is testing something that is specific to a particular framework... This is the general rule... For tests that verify pure SQL behavior, the framework shouldn't matter. Many of the derbyLang tests are meant to test just SQL behavior, so many just run in embedded framework only. Running these tests in other frameworks might generate different outputs so may have to generate different masters. Is there a reason why you would like your new test to run in all frameworks? It seems the behavior is likely to be the same if you specify a userName in the URL. Is there a way to know if a particular test is only intended for one, or some frameworks? Other than running it in that framework and seeing that it fails...? I guess could always run find java/testing -name <testname>.out and see how many master files the test has. Will that work, or is the output compared to a default master if there isn't one for that framework? Looking at 'suites' directory is one way. You could also invoke the tests without actually running them and then see if your test gets picked up in the framework of your interest. RunTest has listOnly option. Satheesh