Cecil Westerhof

I am thinking about writing a desktop application in Java. First I
wanted to use SQLite and truecrypt. (Truecrypt because it will be
installed on an USB stick.) I was thinking about SQLite, because the
data can be accessed with other languages also.

Then I found out that Derby has the possibility to encrypt the
database. That would remove the necessity for truecrypt. I would lose
the (easy) way to access the information with other languages, but the
simplifying made this a good idea.

Now I saw two other Java DB's: H2 and HSQLDB. It is said that the
performance of Derby is bad and that H2 would be a far better
solution. What are the pro's and the cons of the different
possibilities?

--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

John B. Matthews

In article <87mx8io0il.fsf@Compaq.site>,
Cecil Westerhof <Cecil@decebal.nl> wrote:

> I am thinking about writing a desktop application in Java. First I
> wanted to use SQLite and truecrypt. (Truecrypt because it will be
> installed on an USB stick.) I was thinking about SQLite, because the
> data can be accessed with other languages also.
>
> Then I found out that Derby has the possibility to encrypt the
> database. That would remove the necessity for truecrypt. I would lose
> the (easy) way to access the information with other languages, but
> the simplifying made this a good idea.
>
> Now I saw two other Java DB's: H2 and HSQLDB. It is said that the
> performance of Derby is bad and that H2 would be a far better
> solution. What are the pro's and the cons of the different
> possibilities?

All three are fairly transparent. Why not simply compare them with
representative data?

See also <http://stackoverflow.com/q/2746201/230513>.

--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>

Roedy Green

On Thu, 16 Feb 2012 23:51:14 +0100, Cecil Westerhof <Cecil@decebal.nl>
wrote, quoted or indirectly quoted someone who said :

>I am thinking about writing a desktop application in Java. First I
>wanted to use SQLite and truecrypt. (Truecrypt because it will be
>installed on an USB stick.) I was thinking about SQLite, because the
>data can be accessed with other languages also.

Factors to consider:

1. how much hassle does the end user have to go through to install the
database. Some require nothing. They are part of the app.

2. Is it a RAM-only database. Will this be sufficiently large?

http://mindprod.com/jgloss/sqlvendors.html
--
Roedy Green Canadian Mind Products
http://mindprod.com
One of the most useful comments you can put in a program is
"If you change this, remember to change ?XXX? too".