K
kt
I'm developing an application using Java and I would like the user to
be able to plug in various methods of persistance. The has led me to
JDBC using standard SQL-92, but this is really overkill for what I'm
trying to do. I only have a handful of classes that I would like to
persist and I won't be doing any complicated querying on them. I will
always be looking up objects by key values. In addition I would like
to be able to ship a default file based back end with the code for
users that aren't interested in the extra hassle of setting up their
own, more sophisticated, persistance.
I looked at JDO briefly and it doesn't seem to allow what I want. It
looks like the programmer must select the database back end at
development time. Is this correct?
I also thought about using object serialization in some way to achieve
the objective, but this doesn't work. I need to be able to have Maps
that contain more objects than can fit in memory at any given time.
Any suggestions would be appreciated. Thanks.
be able to plug in various methods of persistance. The has led me to
JDBC using standard SQL-92, but this is really overkill for what I'm
trying to do. I only have a handful of classes that I would like to
persist and I won't be doing any complicated querying on them. I will
always be looking up objects by key values. In addition I would like
to be able to ship a default file based back end with the code for
users that aren't interested in the extra hassle of setting up their
own, more sophisticated, persistance.
I looked at JDO briefly and it doesn't seem to allow what I want. It
looks like the programmer must select the database back end at
development time. Is this correct?
I also thought about using object serialization in some way to achieve
the objective, but this doesn't work. I need to be able to have Maps
that contain more objects than can fit in memory at any given time.
Any suggestions would be appreciated. Thanks.