Hi Paolo,
Nice to hear you, you surely have a good experience about database-access.
I like the idea of an embedded database.
I have made some tests in the past with jump+hsqldb, but I didn't get
any memory improvement (I have not much dbms knowledge and I may have
done mistakes leading to some
Paolo,
There were a couple of reasons why I wanted to avoid using a database for
this system. The first reason is complexity. As soon as we start using a
database we begin to deal with things like SQL, JDBC, and database
configurations. We are really attempting to integrate a second peice of very
What about using a Java embedded database like HSQL or Derby???
They already can manage in-memory / persistence of any kind of data
and they do it very well I believe...
You should only keep each Feature's primary keys and, probably, it's bounds.
The db engine will take care of everything else.
Als
