lalinsky/mbslave — Issue #4: Log updated data
Author: sfussenegger
Created: 2011-10-14 08:48:27+00:00
State: open

It would be great to have an optional log for updated data. This could be used to trigger further processing of updates. This could be something as simple as a CSV file in the form `{table};{id};{action}`, e.g. `artist;4234;delete`. There should probably be a dedicated log per update to allow processing files while updates are running.

I'm planning to add this feature myself anyway (never did any Python before though) but I thought that there might be some public interest and/or other suggestions on how to trigger actions on updated data.