Hi bryan,
Thanks a lot for your hints.
I am using derby embedded in my application and it is just one table. I first
thought of doing just one commit for a load, but I guess that is probably not
so well, since for the initial load there are 101004 records each 514 bytes
long to be filled. Is
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
I have no problems doing millions of inserts with one commit at the end in
embedded Derby. Please see my blog for some code details on how to make it
work:
http://mpouttuclarke.wordpress.com/2010/12/10/java-embedded-db-for-ip2locati
on-in-hadoop/
Cheers,
Matt
On 3/9/11 3:40 AM,
Dear Derby group,
I have a desktop client that connects to a derby network server remotely
through JDBC. What is the best way to monitor database connection and give a
feedback immediately if the connection is lost?
Cheers,
Yudi
= = = = = = = = = = = = = = = = =
Yudi Xue
Computer Science
