Monday, November 9, 2015

The beer that broke my database

More than 1 brewer for more than 1 beer
As a data professional this is rather embarrassing, but a beer broke my database. I didn't spill a pint on the server or drop a table in an inebriated fat finger. Paddle Trail Ale by Sierra Nevada AND Crux broke my data model because of my poor planning. When I laid out how data would be organized for this site I failed to take into account that brewers like to hang out with brewers. Probably has something to do with the jovial and friendly product they produce. Collaboration beers are nothing new and I've had my fair share of them (Thank you Widmer), but somehow when I got around to designing the table to hold beers I only allotted for a single brewery. There are other beer advocating sites around that have a similar problem and make use of a notes field. I don't even have that. Just a lone key to a brewery table. I was forward thinking enough to allow for multiple styles as sometime one can't tell the difference between a Russian Imperial Stout and a K├Âlsch. Not saying I've had the conundrum, but I'm sure someone has.

I'm going to fix this problem, but not right now so I'll log this beer as a Sierra Nevada beer. Sorry Crux their name comes first on the can.

No comments:

Post a Comment