Hi to all,

I'd like to do huge manipulation on a single table. Jowning there is a
routine within derby to do bulk imports though, I cannot really use it,
snce there are updates inserts and deletes to be done interpreting some
command field with in each record.

I am not quite sure if it is state of the art to close each time a
prepared statement after it was processed.

While looking at performance things, is it ok to close prepared
statement after each operation, because there might be a pooling within
derby or derby driver for those statements, or should I rather leave
those three kinds of prepared statements (insert, update delete) open
till my manipulation is full done or breaks down for some error?

 

Thanks in advance for a hint

 

 

Malte

 

Reply via email to