RE: :ODBC 1.46_1 released - You REALLY need to test this release

Meir Guttman <[email protected]>
Newsgroups gmane.comp.lang.perl.modules.dbi.general,gmane.comp.lang.perl.modules.dbi.sybase.devel,gmane.comp.lang.perl.modules.dbi.announce
Message-ID <!&!AAAAAAAAAAAYAAAAAAAAAKC25OsDcMdGneFIQhy+Pc3CgAAAEAAAAG9Ic6fvydhKnhXV95ndcnABAAAAAA==@guttman.co.il>
Dear Martin

> -----Original Message-----
> From: Martin J. Evans [mailto:[email protected]]
> Sent: שבת 16 נובמבר 2013 12:34
> To: [email protected]; DBI Developers Mailing List; [email protected]
> Subject: DBD::ODBC 1.46_1 released - You REALLY need to test this release
> 
> I've just uploaded DBD::ODBC 1.46_1 to the CPAN. In the process of
> writing
> http://www.easysoft.com/developer/languages/perl/sql-server-unicode.html
> and https://github.com/mjegh/dbd_odbc_sql_server_unicode I discovered a
> serious bug in the way DBD::ODBC can attempt to insert unicode
> characters into char/varchar/longvarchar columns. This experimental
> release fixes that issue but it does mean this release contains a
> significant change in behaviour.
> 
> The issue ONLY applied to unicode builds of DBD::ODBC (the default on
> Windows) and enabled in Linux/Unix via the -u switch to Makefile.PL.
> 


The DBD::mysql driver supported Unicode/UTF-8 for some times now by turning
ON the driver's 'mysql_enable_utf8' attribute. MySQL also supports UTF-8
text encoding by default.

Do the last changes affect any of this behavior?

(I am sorry that I cannot test your release. I am using ActivePerl, and
ActiveState, as a rule, does not compile and release experimental releases
of packages. I am afraid I'll have to wait until you release a stable one.)

Meir
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.