db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David W. Van Couvering" <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.
Date Fri, 10 Feb 2006 16:06:54 GMT
You should be able to tell by looking what suites it is in.  If it's not 
in derbynetclientmats then it may very well not be able to run with the 
network client.

I too wish all our tests ran with the network client, but we're just not 
there yet.  Maybe someone can do a scan through the tests to see if some 
*could* be added but just haven't yet.

David

Dyre.Tjeldvoll@Sun.COM wrote:
>>>>>>"KAH" == Knut Anders Hatlen <Knut.Hatlen@Sun.COM> writes:
> 
> 
>     KAH> See jdbcapi/users.sql for an example. It seems like you can skip
>     KAH> "jdbc:derby:" from the connection url.
> 
>     KAH> connect 'wombat;shutdown=true;user=francois;password=paceesalute';
>     KAH> connect 'myDB;create=true;user=dan;password=MakeItFaster';
> 
> 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... 
> 
> 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? 
> 

Mime
View raw message