for further hints
Malte
-Ursprüngliche Nachricht-
Von: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
Gesendet: Mittwoch, 9. März 2011 05:30
An: Derby Discussion
Betreff: Re: Performance question, Closing Prepared statements
On 03/08/2011 10:01 AM, malte.kem
[mailto:bpendleton.de...@gmail.com]
Gesendet: Mittwoch, 9. März 2011 05:30
An: Derby Discussion
Betreff: Re: Performance question, Closing Prepared statements
On 03/08/2011 10:01 AM, malte.kem...@de.equens.com wrote:
close prepared statement after each operation, because there might be a
pooling
any derby rule or good practice how many commits are to be
done in respect of how much memory is assigned to the JVM derby resides in?
In general, a commit should be performed at the completion of a
natural unit of work in your application, to tell the database
that you are finished making
-Ursprüngliche Nachricht-
Von: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
Gesendet: Mittwoch, 9. März 2011 05:30
An: Derby Discussion
Betreff: Re: Performance question, Closing Prepared statements
On 03/08/2011 10:01 AM, malte.kem...@de.equens.com wrote:
close prepared
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
On 03/08/2011 10:01 AM, malte.kem...@de.equens.com wrote:
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
