Is there a way to configure derby such that it maintains its transaction state on disk instead of in memory?
I am currently updating 80K rows in a single transaction and am running out of memory. Platform: Ubuntu 8.04 Java: 1.6.0_01 Derby: 10.4.1.3 Driver: Client -- --------------------------------------------------------- Raymond Kroeker
