Hello and sorry,
in an english group i should write not in german,
just wondering why i get no answer ;-(
My Question is, where Results of a SELECT (HSQLDB/JDBC)
are cached and how i can "switch off" the caching.
I called a SELECT in a JUnit Task which first open a
connection to DB, do the SELECT and close the connection.
The program stops.
When I started the program twice, the duration of first
run is e.g. a minute, second run takes 3 seconds. But,
because the program doesn't run during 2 calls, where
are the results cached? Has WinXP its finger in the pie?
And second, how can i switch off the caching? I want to
use the duration of certain SELECTs as a "Benchmark"
to compare one SELECT with another. But cached are
falsified results.
Can you please give me a hint, who is caching (i think
not HSQLDB?) and how i can avoid it?
TIA, Det
|
