Caught by the old 'SQL injection' trick

[shoei_mike]

Comments

[marsden_online]

Heh. I've been dealing with a lot of that recently.

[shoei_mike]

Fortunately, my stuff will go from a front-end app on a Windows client to postgreSQL on the server. I don't have to worry much about the script kiddies.

[mattmatt]

It's a silent backslash. Let's face it, it's not the least pronounceable Gaelic name out there.

[shoei_mike]

"Silent backslash" would be a great name for a band.

[cookiemon]

I won't go into how it got there, but I found one of those in some code I'd written that was in beta, i.e. trials outside the company (that part of the map that's marked "here be O'Connors"), it was more embarrasing than that time I managed to recursively remove every key in my registry.

Good times.

[etfb]

Just wanted to say that there's a solution for dealing with programmers who (a) don't allow for apostrophes in names stored in databases, or (b) (worse) expect you to put up with backslashes appearing in user-visible input/output to handle that situation. Here's what you do:

Take one syringe.
Fill with equal parts caustic soda, blue-green algae and cat urine.
Inject into programmer's brain stem.
Watch as he screams in agony and dies.
Hire programmers who don't do stupid things.

I hope this helps!

[shoei_mike]

Wonderfully helpful... except that I'm the case-a type naughty programmer with epsilon experience in SQL. Oh well, "yay!" for testing.

Your solution pun reminds me that if I'm not part of the solution, then I must be part of the precipitate.