Slim down database usage

seantis / seantis.dir.events

Events Directory for seantis.dir.base

1 stars 2 forks source link

Slim down database usage #70

Closed href closed 10 years ago

href commented 10 years ago

There are currently two issues which contribute to a huge DB file for Zug and Bern:

Normal lookups of views and kml-documents are logged as a transaction. Something is being written and it ends up in the log.
Guidle events blow up the database like crazy.

This should be investigated.

msom commented 10 years ago

seantis.dir.base.core.KMLDocument.features triggers a transaction.

Maybe use an adapter to annotate the settings as in collective.geo.contentlocations.geostylemanager? https://github.com/collective/collective.geo.contentlocations/blob/master/src/collective/geo/contentlocations/geostylemanager.py

href commented 10 years ago

That's exactly what I had in mind. I'm not sure if it didn't exist when I started with seantis.dir.events or if I tried it unsuccessfully. Anyway, if this can work, then it would be much better and cleaner.

msom commented 10 years ago