Weevil Genius

Sooner or later when dealing with data that contains addresses, you’ll need to perform distance calculations. Some examples might be “which store is nearest to location X” or “display all hotels within 20 miles of the customer’s location sorted by distance”. This post deals with such calculations based on positions designated by latitude and longitude. The process of determining the latitude and longitude of an address is called geocoding and is outside the scope of this article.

A join in SQL is an attempt to match up rows in one table with rows in another. This allows you to treat the joined rows as if they were in one big table. The differences between the various join types mostly have to do with whether and how non-matching rows are discarded. Everything discussed below is generic SQL and not specific to MySQL unless noted. I use “record” and “row” here interchangeably.

Have you ever wondered which version of MySQL supports a particular feature? I certainly have. Here is a table listing various major features and storage engines and which versions of MySQL support them, from 3.23 through 5.1. I have cross linked to the MySQL online manual wherever possible, though there are still some gaps.

I have long been interested in creating my own custom playing cards, partly because I like to tinker, but mostly because I would like to be able to recreate out of print board games that contain cards. In particular, I was originally inspired to do some of this research in order to reprint a decent copy of Wiz War which I enjoyed playing with friends in college.

What follows is the notes and resources I have gathered so far in pursuit of this project