That's great, it starts with an earthquake, birds and snakes, an aeroplane... Lenny Bruce is not afraid...
Sorry, but that was the first thing that popped into my mind when I read this article this morning. Yeah, I'm probably overreacting, but still the idea of everyone's favorite little open source database getting gobbled up by the folks that brought us Solaris is, well, a little disheartening.
All sorts of speculati...
When we last heard from Our Hero, we’d begun the joyous process of creating a simple Google Maps/Amazon mashup. We took a peek at what the finished product should look like, we obtained our Google Maps API key, and we created our database tables and populated them with some data. All good things.
We also talked about geocoding, that process of converting a street address into the coordinates (longitude and latitude) that Google Maps digs. Our LOCATIONS table has some street addresses and empty columns just hankerin’ for some longit...
And now for something completely different…
Sorry to disappoint all the little nerdlings who come around here only for the Drupal goods, but today’s post won’t be at all related to our favorite CMS. We’ve talked about different Drupaly topics for weeks, now it’s time to shake things up a little. Today, kids, we’re going to make a basic Google Maps mashup.
Yeah, I know. The world needs another Google Maps mashup like I need a hole in my head, right? Who cares. They’re fun, and we’ll try to make our s...
In our last SQL post, we talked about the three basic types of JOINs enterprising young SQL junkies might use to gather data from different tables in their databases.
"Enterprising..." Oh, how I crack myself up some times. Seriously. Don't make me explain why that's funny.
Anyway, in between Star Trek-related examples, we blabbed on and on about INNER JOINs, three kinds of OUTER JOINs, and the almost completely useless CROSS JOIN. You might remember, though, that every one of those brilliant examples involved querying existing data with SELECT statements. T...
When you've been playing around with SQL for awhile, you start to take your knowledge of JOINs for granted. When someone asks you about JOINing data from two or more tables together, you get this stunned look on your face... You know, the same one you get when you actually hear someone mutter the words "I've never seen 'Star Wars'." You forget that you, too, once didn't know a JOIN from a Jedi, and that everyone has to start somewhere.
So let's talk about JOINs. Like the name implies, a JOIN is simply a method for connecting two tables in a database, usually through so...