BONNEFILLE Guilhem <[email protected]> writes: > An other solution is to compress (gzip) old part of history as we > never need to update them. > > Is it possible to do this with Derby?
Derby doesn't have any built-in compression facilities. You say you don't perform updates (or deletes), so presumingly there are no holes in your database files, so running compression wouldn't help[1]. Some ideas: Could you compress the lob contents before you insert them into the database and uncompress on retrieval? Could you store the lobs as compressed files and just let the database reference them? Did you consider a compressing file system? Thanks, Dag [1] http://db.apache.org/derby/docs/10.7/ref/rrefaltertablecompress.html http://db.apache.org/derby/docs/10.7/ref/rrefproceduresinplacecompress.html > Do you have any other tips when faced to this use case? > Any other (embedded) database that best matches our needs? > > Thanks for your answer. > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program.
