The Kosmala Blog

So on one of the message boards I frequent, there was a thread about the first video/computer game you ever played. My thoughts immediately turned to playing the original Super Mario Bros., and being too scared to play it at first. So I let Margaret play and watched.

But then I saw one post from someone who said their first game was Rocky’s Boots:

“Holy Crap!” I thought to myself, “I remember that game!” That was the game where you had to solve puzzles by creating wiring through various logic gates (like AND, OR, and NOT). It had all sorts of shapes and colors and taught you about how computers worked (although as a small child I wouldn’t realize it at the time).

Then I recalled another game that involved similar gameplay but was a bit more mature. In that one you programmed robots to do your bidding, and each robot had a lot of different features like thursters, contact panels, a grappling claw, a peroscope. You had to wire the robot specifically to do a task and then set it out to solve various puzzles in this make-believe world. Sometimes it had to get a key, sometimes it had to cooperate with another robot to get around a security drone. I remember spending hours playing this with my sister. Luckily I found the name pretty quickly: Robot Odyssey. I don’t think we actually every beat it, or at least I don’t remember beating it, but apparently there’s a java version of the game now that’s playable on modern computers.

Screw World of Warcraft and my Playstation 2, I’m playing a 23 year-old game when I get home.

Today was one of those days, where at the end of a 3 hour bug-finding mission, you want to scream.

The problem: one the support gals was having trouble running a particular export for a client. An export is basically just an extraction of specific data from the system to give to a client in a format that client wants. The specific error message was pretty vague: something about a field being truncated and loss of data.

The first clue was that this was a SQL error, because only SQL will crap out on something like that. While VB or most object oriented languages will simply convert or truncate a field for you, SQL is very strongly typed and won’t let you do that. I found the stored procedure (bunch of SQL code) for that particular export and took a look. Unfortunately there were about 50 or so fields being extracted, and one of them was causing problems. Sadly for me there’s no nifty way of figuring out which one it is. The error simply said “a field”, so I would have to go through them in chunks to figure it out. An annoying aside to this is that I had to actually mark each field three separate times in the file in order to test it, making things even more cumbersome.

I decided to do it in chunks. First I would try all the address-related fields because they are fairly similar. Then I would deal with the product fields which had quantity, price and other such information. Luckily the first chunk was the culprit because when I commented it out (removed it from being in the script) it worked fine. So I was left with 10 or so fields, and I thinned those down one by one until I eventually came across the field “ContactFirstName”. What this means is that in all the records returned by this SQL code, one of the contact’s first names is funky… most likely it’s too long (hence the truncate error).

The next step was to isolate the specific records I needed, which required a daring and creative amount of cut & pasting. Then I got the code to spit back all the first names. There were a few hundred rows returned. “Bob”, “Andrea”, “Phillip”, “Mary”, all pretty normal names. Then I found it. I came across a field containing “ANGELA, MICHAEL, BRANDON, TYLER, AUSTIN, KAITLYN, HALEY WHITE”, which is a hell of a first name. To test to see if this was the culprit, I parsed it down to just “Angela”, ran the export and got no errors.

So I found the problem after a few hours of hacking my way through a convoluted SQL file while being remotely connected to a client, which slows everything down a lot. The eventual error was that the ContactFirstName field in the export was 30 characters long whereas it was 50 characters everywhere else in the application. The creative name above happened to be more than 30 characters. The solution? Change the ‘3′ to a ‘5′, and I’m done. That’s it.

Sigh.

So yesterday was the 4th of July, the annual holiday where everybody in the East End decides to be nice to each other for a day. Seriously, it’s like a big block party where I live. Lots of people having barbecues, lots of people walking around, lots of live music going on, just a busy people day. The weather wasn’t fantastic: overcast most of the day, breezy and a bit chilly. But that didn’t deter people from having a good time and getting really drunk. While I refrained from most of the alcohol consumption, I did get to see the powerfully amusing combination of fireworks and booze. Now I didn’t see anyone blow their head off, but there were plenty of rogue firecrackers going off throughout the day.

I headed back home around 8:30 to check some things before going to see the fireworks display down on the Eastern Prom at 9:15. Well at about 8:45 I heard a lot of banging, so apparently they started early. I walked down the street a bit and got a real nice view between two houses, so I just stood there and watched. And then about ten minutes into the show I realized why they started early: it began to absolutely pour. Now I love the rain, and I like fireworks on cloudy days (because the colors bounce off the clouds), so I was happy as a clam watching, but I imagine those who had parked their butts down on the Prom with no rain gear were probably pretty unamused. The show itself was quite long, about 30 minutes, and pretty good for a local show. Lots of big colorful ones, and a mix of interesting shapes ones, and a couple big bangers. My favorite sequence was one where they shot up about a dozen or so of those streamer fireworks that explode and kind of linger. It was real pretty.

Having a day off in the middle of the week was great, and even though I’m back at work today, it’s deader than doornail here, hence my work-day posting. Tomorrow will probably be similar… perhaps I should go make some bugs to fix.