Subject | Re: another Proble with Embedded Server |
---|---|
Author | Roman Rokytskyy |
Post date | 2004-04-26T17:59:15Z |
Hi,
just your application with the database on which it can be reproduced?
I can sign an NDA if needed. Please contact me privately if this is
possible.
An alternative would be to build driver direct from CVS (that is
relatively easy, just use build.bat) and insert some debug statements
in createStatement() and executeQuery(String). Also you can wrap the
code inside these methods with
try {
...
} catch(SQLException ex) {
ex.printStackTrace();
throw ex;
} catch(RuntimeException ex) {
ex.printStackTrace();
throw ex;
} catch(Error ex) {
ex.printStackTrace();
throw ex;
}
to see if really no exception is lost. What you write stresses my
belief how Java works, therefore I would like to double check it. :)
Thanks!
Roman
> Please excuse me for my unfriendly stüle of writing...but is wasNo problem at all. :)
> late and stressfull.
> The ResultSet below runs pretty good on a normal driver, on delphiOk, it becomes interesting.
> with embedded I've not testet it.
> The Strange thing is: if I make A brakpoint onIs it possible to get either test case that reproduces the problem or
> ResultSet re = main.getWman().getConnManager().getFbConn
> ().createStatement().executeQuery(this.MAIN_SQL);
> (MAIN_SQL is the statement below)
> and one below the point below will neveer be reaches, it is like a
> return is between it, and because it not stops (the aplication runs
> like an empty statement wher there) I cant check if the statement is
> null or else. And: There is no Exception or Error!
> A Statement like
> "SELECT COUNT(*) num FROM meldungen"
> will be executet without any problems.
just your application with the database on which it can be reproduced?
I can sign an NDA if needed. Please contact me privately if this is
possible.
An alternative would be to build driver direct from CVS (that is
relatively easy, just use build.bat) and insert some debug statements
in createStatement() and executeQuery(String). Also you can wrap the
code inside these methods with
try {
...
} catch(SQLException ex) {
ex.printStackTrace();
throw ex;
} catch(RuntimeException ex) {
ex.printStackTrace();
throw ex;
} catch(Error ex) {
ex.printStackTrace();
throw ex;
}
to see if really no exception is lost. What you write stresses my
belief how Java works, therefore I would like to double check it. :)
Thanks!
Roman