Hi Mallah,
I had this problem once, and put together this bunch of regexes. It's
by no means optimal, but should solve 90% and would easily be adapted
into a plperl function.
Begin perl:
$value =~ s/[\xc0-\xc6]/A/g;
$value =~ s/[\xc7]/C/g;
$value =~ s/[\xc8-\xcb]/E/g;
$value =~ s/[\xcc
Full disclosure on previously posted Perl code: I think I may have
cribbed all or part of that previous code from something (Perl
cookbook?). In any case, the issue is essentially a mapping of which
ascii codes "look like" low-ascii, so I don't think there are any
authorship issues.
Best,
Ra
Hi John,
(added to JDBC list)
1. What is your database encoding? Does it support the unicode OK?
2. Are you sure it's getting /stored/ as a question mark rather than
just displayed as such? Remember, if it is stored correctly, but you
look at it from a terminal that doesn't support the charact
Hi Nicholas,
CHAR fields, as opposed to VARCHAR, are blank-padded to the set length.
Therefore, when you inserted a < 25 character string, it got padded
with spaces until the end.
Likewise, when you cast '100058' to a CHAR(25) in the = below, it
gets padded, so it matches.
The LIKE operat
Wow, I had never actually faced this problem (yet) but I spied it as a
possible stumbling block for porting MySQL apps, for which the standard
practice is inserting a NULL. As I have made a fairly thorough reading
of the docs (but may have not cross-correlated every piece of data yet,
obviousl
