tag:blogger.com,1999:blog-5822946.post4296558007383994339..comments2014-09-17T10:15:34.033-05:00Comments on Marc's Musings: Please tell me the rest of the code doesn't look like this...IDisposablehttp://www.blogger.com/profile/02275315449689041289noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5822946.post-37277164507851477642009-12-02T07:14:54.000-06:002009-12-02T07:14:54.000-06:00Hahaha. I was reading your blog. This is great. ...Hahaha. I was reading your blog. This is great. I've seen things like this done before and it always makes me want to cry. :P In the particular case I'm thinking of, it was in C++, but the concept is the same. In my own experience, I typically use stored procedures, which mitigates a lot of the risk you were mentioning.The Software Purist (http://www.softwarepurist.com)noreply@blogger.comtag:blogger.com,1999:blog-5822946.post-46657861763185805212007-08-15T09:00:00.000-05:002007-08-15T09:00:00.000-05:00That's pretty awesome. (Aren't SqlParameters grea...That's pretty awesome. (Aren't SqlParameters great?)Brian Dukeshttps://www.blogger.com/profile/07026014589345008284noreply@blogger.com