- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Hello world was too many characters to echo
Admin
WTF mate?
Admin
I liked the typo....
"asdfasf"
Where'd the 'd' go? I can understand now why it had to print hi.
Although I can understand personalized comments. I HATE with a passion when I'm told to do something but don't know why. I usually put a comment like that in code. It's called
cover your arse.
You know - along the lines of
/* This is a hack to write a log to a temp file and MUST be removed for production, but I bet it doesn't and ends up crashing the server when it runs out of disk space */ :-)
Admin
Some coders get lonley and need someone to talk to. Some go out and meet up with friends, some write procs to talk to them!
Anyway, at least he/she didn't actually call it sp_hi....
Admin
Common practice in my company...
Admin
hmmmm, one issue with this is that the "hello world" aspect would only work from
query analyzer, T-SQL PRINT statements are un-retrievable from client side code.
ADO or ADO.Net. So, I guess the fact that the proc ran from the client was good
enough to ensure connectivity?
Admin
Doesn't the SqlConnection.InfoMessage event allow you to get PRINT statements?
Admin
Please Please Please post more of this code.
Brian - yes, InfoMessage will print error messages - supposed to only print errors w/ severity < 13 (or maybe it's 11) but Print statements will show even though they aren't errors.
Admin
Hey! It's my code! ... Err... nevermind hides
Admin
Who added the sp_ prefix?
Admin
Thanks Brian, and Bill, I was not aware of that event.
Admin
It's a hidden easter egg. :-)
Submit to www.eggheaven2000.com