I had to robustify a database layer that was talking to a DB that couldn't store a range of characters including single quote and other punctuation. Also some of the calling code, which I wasn't able to touch, would fail to escape quote characters properly.
Code snippets:
sub fix_dodgy_chars
{
my $s = shift;
$s = '' unless defined $s;
$s =~ s/[:;<>\[\]`{|}\000-\037£]/ /g; # replace dodgy chars with sp
+ace
$s =~ s/\'/\_/; # single quote translated to underscore
$s;
}
sub Prepare
{
...
# map non-escaped embedded single or double quotes to underscore where
+ neither at end of line
# nor followed by semicolon, comma, whitespace or rightbracket
$sqlstring =~ s/([^\\\s\,\(])([\'\"])(?!($|[\;\,\s\)]))/$1_/g;
# then examine quoted strings and replace characters that sql cannot h
+andle, currently
# : ; < > [ ] ` { | } &
$sqlstring =~ s/\"([^\"]*)\"/'"'.fix_dodgy_chars($1).'"'/ge;}
...
}
-- peterdragon
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|