in reply to Re^3: Encoding issue from DBI to string
in thread Encoding issue from DBI to string

The SQLi point I raised is unrelated to the encoding issue. It's a common attack vector, people generally aren't aware of security issues when they start coding.

  • Comment on Re^4: Encoding issue from DBI to string

Replies are listed 'Best First'.
Re^5: Encoding issue from DBI to string
by karlgoethebier (Abbot) on Jan 04, 2013 at 10:16 UTC

    Yes, shure - you are right, no question. But perhaps your answer wasn't as helpful as intended in this context?

    Best regards, Karl

    P.S.: But what the hell causes this encoding issue?

    «The Crux of the Biscuit is the Apostrophe»

[reply]

      "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.

[reply]
        "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]

In Section Seekers of Perl Wisdom