Nick Wellnhofer wrote: > On 15.04.2010 06:25, fREW Schmidt wrote: >> IIRC ForceUTF8 actually hasn't worked at all for the past 4 years. If >> you think it does, check again. > > It has always worked for me. I also read the warning in UTF8Columns.pm > that claims that ResultSet/create doesn't send encoded values to the DB. > But I can't confirm that. I get properly encoded values. > > OTOH, it looks like I can simply use an old version of UTF8Columns if > you decide to remove it. >
We are not removing it, but it does not work *today* and there are no plans to fix it. As a very simple test look at the output of DBIC_TRACE and see what is actually sent to the database (you'll find it is not bytes but pure unicode). The only thing that made things work for you is that the database somehow knew what do to with the unicode. In which case it is very possible you do not even need UTF8Columns. _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
