Automatic removal of old db4o data

[GoogleCodeExporter]

1. Feature Description

I wish that the db4o.persist configuration would include a parameter which 
specifies the max age the given items persistence may reach. The persisted data 
exceeding this limit should automatically be removed, and thereby avoid db4o to 
grow infinitely. The size would not be fixed, but depend on the "traffic" for 
the given variable. 

I'm aware of the recently added queryable property of rrd4j. That's great, but 
for other purposes. Rrd4j is perfect for data like temperatures etc.

2. Example Use Case
Information like binary inputs (presence, door contacts), etc does not make 
sense in rrd4j. I want to persist them, query them (with reliable reply) and 
still not grow infinitely.

Also for restoring relay states for a given moment, you probably want to prefer 
db4o rather than rrd4j.

Original issue reported on code.google.com by kristian...@gmail.com on 23 Apr 2013 at 11:13

[GoogleCodeExporter]

I actually planned to have something like a filter in the persist file syntax - 
which could be set like "filter all data newer than a month" or "filter only 
last 100 entries". If such a filter is defined for an item, it means that the 
persistence service could automatically purge older values. I didn't find the 
time to implement that yet though...

Original comment by kai.openhab on 29 Apr 2013 at 9:08

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by kai.openhab on 22 May 2013 at 8:15

[GoogleCodeExporter]

Migrated to https://bugs.eclipse.org/bugs/show_bug.cgi?id=423508

Original comment by kai.openhab on 7 Dec 2013 at 8:59

• Changed state: Invalid