Re^6: Encoding issue from DBI to string

"But perhaps your answer wasn't as helpful as intended in this context?"

You mean my response which linked to a wikipedia article explaining in detail the problem, a link which shows how to resolve the issue in Perl/DBI and a cartoon illustrating the issue of blindly trusting user input? ev0lution seemed to understand the point I made.

Comment on Re^6: Encoding issue from DBI to string

Replies are listed 'Best First'.
Re^7: Encoding issue from DBI to string by karlgoethebier (Abbot) on Jan 04, 2013 at 13:11 UTC
"You mean my response..." Yes. Now ev0lution knows how to avoid SQL injection but he still gets some weird output. His problem still persists. Best regards, Karl ŤThe Crux of the Biscuit is the Apostropheť	[reply]
Re^8: Encoding issue from DBI to string by marto (Cardinal) on Jan 04, 2013 at 13:25 UTC
My only input in this thread has been on the subject of SQL injection. This was my intention. Your statement "But perhaps your answer wasn't as helpful as intended in this context?" is confusing as my response (again, not to the encoding issue) was clearly of use to them, albeit with a problem they didn't even know they had. Often on perlmonks people reply to posts pointing out problems/issues with code which are unrelated to the question the user is asking. Often this is because the user is totally unaware of the problem. This is a perfectly valid thing to do.	[reply]
Re^9: Encoding issue from DBI to string by karlgoethebier (Abbot) on Jan 04, 2013 at 13:46 UTC
Thank you very much for clarifying this. I was confused ~~too~~ a little bit. Best regards, Karl ŤThe Crux of the Biscuit is the Apostropheť	[reply]