Re: UTF8 vs SQLite

Eventually I chose this solution:

use Data::Structure::Util qw/_utf8_on/;

$some_cdbi_class->add_trigger(select => sub { _utf8_on($_[0]) });
[download]

-nuffin
zz zZ Z Z #!perl

Comment on Re: UTF8 vs SQLite Download Code

Replies are listed 'Best First'.
Re^2: UTF8 vs SQLite by Your Mother (Archbishop) on Jan 14, 2006 at 23:00 UTC
Late in the game, I know. This is working for me too and it may be the solution I keep till the DBD::mysql is fixed. I think the recursive sub is probably not needed, right? Just the regular `utf8_on` instead of the `_utf8_on` in your sample.	[reply] [d/l] [select]
Re^3: UTF8 vs SQLite by nothingmuch (Priest) on Jan 14, 2006 at 23:03 UTC
IIRC (i haven't played with this code in a while, don't have convenient access to it in the weekend) I did the recursive sub because it was already an object in the trigger. WRT mysql - gaal submitted a patch - use it. I heard it won't be applied because the authors would like more complete support, but it's not likely that will happen. -nuffin zz zZ Z Z #!perl	[reply]