Re^3: Why does perl not mark variable as utf-8?

I believe, that if use utf8 is in scope, all literals are marked as utf-8, but note that that only works on string literals. If you're reading strings from anywhere else, you still need to make sure they're upgraded in some other way.

By the way, the reason DBD::mysql currently doesn't upgrade all input is that it's not immediately clear which data/columns should be utf-8 text (and should be upgraded) and which is non-utf8 text or binary data (and must be left alone).

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^3: Why does perl not mark variable as utf-8?

Replies are listed 'Best First'.
Re^4: Why does perl not mark variable as utf-8? by Anonymous Monk on Aug 29, 2007 at 14:59 UTC
Is that true? DBD::mysql apparently know what columns to mark on the way out. "When set, a data retrieved from a textual column type (char, varchar, etc) will have the UTF-8 flag turned on if necessary." Is that because of column metadata that is provided with the results of a select?	[reply]
Re^5: Why does perl not mark variable as utf-8? by Joost (Canon) on Aug 29, 2007 at 15:14 UTC
Yes, that's exactly it; when retrieving a result set, there's enough metadata to determine weather the columns are utf-8 text or binary, but when executing a query it's hard to figure that out. It may be possible, but I've given it a try and couldn't find a good way to do it in the limited time I had. See also http://rt.cpan.org/Ticket/Display.html?id=25590 "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]