If I read correctly, there are only 2 ways to solve this :
* bug DBD::mysql maintainer to have the fix included. Would require an
official release, an upgrade of DBD::mysql, but it's a better solution
in the long term.
* modify EVERY SQL query to Encode::decode_utf8() every value. A quite
huge task !
I have modified one script (marc_subfield_structure.pl), and everything
works fine with Encode::decode_utf8 (and don't work without it)
Paul POULAIN et Henri Damien LAURENT
en logiciels libres et bibliothéconomie (http://www.koha-fr.org)
I've sent an email to Patrick, who maintains the CPAN module and
also appears to work for mysqlab ... I'll let you know if/when he
replies with an answer to our questions.
> * modify EVERY SQL query to Encode::decode_utf8() every value. A quite
> huge task !
This is true, but it's also an excellent opportunity to put thd's
recommended abstraction of the underlying SQL database. I'm more than
happy to do some grunt work if we have a clear path for how to
implement thd's proposal. Any thoughts on how best to acomplish
Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE
President, Technology migration, training, maintenance, support
LibLime Featuring Koha Open-Source ILS
[hidden email] |Full Demos at http://liblime.com/koha |1(888)KohaILS