Hi and thanks a lot for the information :)
I have still a problem with Encode::decode_utf8. If the string to be decoded is already UTF-8, Encode::decode_utf8 returns an empty string! There seems to be no way to check if decoding is necessary, because in both cases (decoding successful or empty string), the string to be decoded was marked as "not utf" when I test it with Encode::is_utf8 .
Is there a good way to avoid this problem?
And what will happen, if a future version of DBI and DBD already handles the SQL data correctly? Will the decoding still work, or do we have to re-write all scripts then?
I would be glad to get an answer here, maybe Patrick has something to say that solves my problems?
Thanks in advance
Ingo