06-10-2011
//
http://pagead2.googlesyndication.com/pagead/show_ads.js
We all get that day when we get an exception complaining about the single quotation or apostrophe that was in our SQL statement.
The best advisable thing to do is to use stored procedures so that all data are passed as parameters. However there are situations we have to use in-line SQL statements and even there are situations where even SQL parameters cannot manage this issue.
For example, if you use the exec method in you stored procedure body to do some dynamic stuff [read more about using exec to generate dynamic queries in stored procedures here ] you will have noticed that even if you pass a string with an apostrophe to an sql parameter it will still throw an exception at you !
So the only way out is to escape this character. Once you instruct the SQL parser to escape the character it will take the apostrophe as part of the string input not part of the command.
How to?
Simply replace your apostrophe / single quotation with two apostrophes / two single quotations .
i.e.
Replace Bob’s world With Bob’‘s world <- these are two single quotation characters (not one double quotation character)
This can be easily done by using the string.replace method.
Was this post helpful to you? How can I improve? – Your comment is highly appreciated!
Cassian Menol Razeek
I Learnt Today 