Could be. I've been trying to bite off a different pieces of this elephant over time and what you are describing here is the easy part. I was still going by [our agreement](https://github.com/gittip/www.gittip.com/issues/1549#issuecomment-26758572) of not inverting the code yet. Until we get our data story straight (#1939), I see no point in doing so.

Chad, I fear or overengineering here. Let's try first to get the data into one log/events table and get rid off all the different log_* tables and log changes we have not been logging yet. After that keep adding self checks trying to rebuild different parts of our application state from the logs/events. And lets see where it brings us. When we know what we want to do with our data we can worry about inverting the code and using the events architecture for other new cool tricks.

What I want to do is weekend-sized PR. Anything larger is not going to work. Dragging the PRs weeks and weeks is depressing. We can fix this one (change the schema of `events`) but let's have more work in next week's PR.