[Seaside] Goods database becoming huge

[Samuel Tardieu]

Hi.

I have a Seaside application which uses a Goods database. I have a
problem with this database becoming very huge:

-rw-r--r--  1 goods  goods         68 Oct 13 02:03 edt.cfg
-rw-r--r--  1 goods  goods          8 Jan 23 20:54 edt.his
-rw-r--r--  1 goods  goods  268435456 Jan 24 14:56 edt.idx
-rw-r--r--  1 goods  goods       6544 Jan 24 13:59 edt.log
-rw-r--r--  1 goods  goods    8388608 Jan 24 14:56 edt.map
-rw-r--r--  1 goods  goods    5709824 Jan 23 20:54 edt.odb

The structure of this database is as follows:

root (Dictionary with 4 entries)
|
+----- 'DayListing' (Dictionary with 1 entry)
|      |
|      +---- #bci1a (Dictionary with 24 entries)
|            |
|            +---- object1
|            |
|           ...
|            |
|            +---- object24
|
+----- 'Persons' (Dictionary with 4 entries)
|      |
|      +---- object1
|      |
|     ...
|      |
|      +---- object4
|
+----- 'lastChange' (object)
|
+----- 'lastRefresh' (object)

None of the objects contains references to dictionaries or structures
with a large size. The database keeps growing as I add data in the
#bci1a dictionary -- older objects in this dictionary gets removed
every hour, this dictionary never contains more than 30 entries.

How can I check if some objects are present in the Goods database
while being unreachable from the root?

  Sam
-- 
Samuel Tardieu -- sam at rfc1149.net -- http://www.rfc1149.net/sam