Schema Revision and PoliticalPorn

I got to my sillyDayJob early this morning so I could work on my SQL query because using JSON and javascript methods got the same weird results. I went to print out the picture of my revised schema and saw the image was more out of date than I thought so I opened it in Photoshop and updated it.

I keep wanting to just put all of this information in one table but I’m very stubborn about wanting to master SQL for properly normalized databases. While working on that, some lady came into our office and asked if I would be interested in a League of Women Voters guide to amendments on the ballot. Would I? I jumped up and shouted, “And how!” No, actually I didn’t but that’s how I felt. I then really wanted to be all Mad Men and shout, “Thanks, this is sure swell!” because … obviously, I’m just a big geek.

It feels good to be a political geek again.

Yes, people in Florida can read. Yes, people in Florida vote. *sigh*

Hmm … a couple of those don’t show the table’s primary id column. [Below I have an updated update of the revised revision.]

But … already … I think I know how it should and will work.

In related news, two of my pull requests for Hacktoberfest are for OpenElections repos.

Which … makes me sad … because it makes me think about the fact that if openFEC provided election data through their API instead of jacked up PDFs, etc. then … the fine folks at OpenElections wouldn’t have to work so hard.

Update 13 hours later: Getting closer …

Screen Shot 2018-10-12 at 7.14.39 PM.png

There’s probably a better way to do it, but … it’s working (so far) and that’s all I care about at this point.

Screen Shot 2018-10-12 at 7.14.14 PM.png

Here is the corrected revised revision of the revision.