Aaron Williams

I solved this by just adding the field to the column: ``` sql ALTER TABLE league_season_scrape_module ADD is_active tinyint(4) NOT NULL DEFAULT '0'; ```

This continues #152

+1 to creating a `person` table. Currently, we're not really tracking folks like treasurers, agents, etc. and I'd love to have a way to follow and link those folks together.

This could possibly be due to the database engine. InnoDB vs MyISAM. Investigating some more

Solved by adding `init_command` value to `OPTIONS` key in `DATABASES`. See: http://stackoverflow.com/a/9699805/868724 Not sure how often this could happen, but it may be worth adding to docs @palewire ``` python...

I think I ran into this error because I was working with Django migrations. I'm not entirely sure what happened, but I started seeing this error AFTER I started using...

Ahh that makes total sense.

Well, we have a lot of direct support for CSV already in these projects so I'm inclined to support CSV exports. That said, there's no reason why we couldn't implement...

It's worth noting that CSV exporting for the `Expenditure` and `Contribution` models just landed in PR #175. It should be fairly trivial to write the view and use Django's [`StreamingHTTPResponse`](https://docs.djangoproject.com/en/1.7/howto/outputting-csv/#streaming-large-csv-files)...

Clearly, we can only sum on the Summary table, but it's got to see how the export worked. Looks like there's an issue with how full_name is loaded on Expenditures