in my previous node

we decided that for the queries like this:

my $sql = "SELECT a FROM table WHERE (a ~* (E\'.*\' || ?))";

quotemeta is enough to stop users sneaking in reg expression into the queries. and it probably is.

unfortunately quotemeta also quotes unicode characters what makes the situation unacceptable in majority cases:

DBD::Pg::st execute failed: ERROR:  invalid byte sequence for encoding
+ "UTF8": 0xd05c
HINT:  This error can also happen if the byte sequence does not match 
+the encoding expected by the server, which is controlled by "client_e
+ncoding". at

[download]

thus i think we need to come up with a better resolution.. ;-)

thanks

In reply to postgres reg expression quoting (again) by zdzieblo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.