Closed myersjustinc closed 9 years ago
Thanks for this bug report. I believe you've put your finger directly on the problem.
During the implementation of the improved PostgreSQL loader I discovered that a smattering of our raw models contained fields that were in the official documentation but absent from the actual data dump. Our previous loaders just skipped over them.
My suspicion is that the state has chosen to withhold these fields from release. Since they tend to be fields related to addresses, my guess is that it the redaction due to a (questionable) interpretation of privacy protections. Sometime soon I'd like to do a comprehensive study of all fields withheld from the data dump but I haven't made the time yet.
Solving your bug in the short term I believe will require that we subtract from the campaign browser loader's custom SQL all of the the fields deleted from the raw app.
This is unintended consequence of my earlier work and I apologize for the pain. I'll try to get to a patch later today.
Alright. I took a blind stab at removing two of the retired fields. Haven't had time to test but it's a start.
Alright. I think I fixed this. After pulling the latest code, the expenditure loader now works for me.
Yep, works for me, too. Thanks for that fix!
The
buildcalaccesscampaignbrowser
management command fails partway through:That traceback points to this query, which refers to a field that used to exist but no longer does.
That field disappeared in california-civic-data-coalition/django-calaccess-raw-data@8e6749932b711c8ce3921a00f27cf4d1fa82d4bc, and this query seems not to have been updated to match. Not entirely sure I follow what was going on with the
django-postgres-copy
changes (especially since I'm using MySQL for this), so I haven't attempted to put together a fix—but figured I should flag it anyway.(Noticed this while I was working on #149, which I've otherwise made good progress on...)