sorry for the typo it should have been 15 bytes not KB i wont be
reading the same records over and over again once i read them i will
calculate and put the result in cache so i wont be reading the same
records until next reboot what i want to do is make that initial read
as fast as i can.
Does anyone know if Derby is affected by this years Extended Daylight
Saving Time? If so, is there a fix?
Darryl Bowler wrote (2007-01-25 14:33:13):
Does anyone know if Derby is affected by this years Extended Daylight
Saving Time? If so, is there a fix?
Derby is indirectly affected through the Java VM. If the VM is correct,
then Derby will behave correctly.
You will have to check out the VM
I just came across this article on java.net, thought people
on this list might be interested in it:
http://today.java.net/pub/a/today/2007/01/16/synchronizing-web-client-database.html
Nice work, David!
thanks,
bryan
I'm trying to debug a deadlock. There are two transactions: one updates
rows from table foo, and one selects the same rows from table foo for
reading. Is it possible to get in a deadlock in this situation? I'm
using the default READ_COMMITTED transaction level. The transactions
look like:
