From how I interpret the comments regarding the SQLite changes between 2.8 and 3.x, SQLite doesn't care what kind of data you hand it. I'm not sure if DBI provides some hooks or ways to automatically tag all (outgoing) strings as UTF-8 though - if you're using Class::DBI, you can put the conversion/tagging into a trigger, but I guess if DBI doesn't provide, you have to use Scalar::Util yourself to add the UTF-8 tag. Or maybe barts tagging trick via pack or unpack works:

my $utf8 = unpack "C0", $value;
# but bart will likely correct my incorrect usage

[download]

In reply to Re: UTF8 vs SQLite by Corion
in thread UTF8 vs SQLite by nothingmuch

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.