Just a thought, also add another flag to explicitly use the buggy code even if it is the default. That option would just suppress the warnings for now. ('mysql_enable_depreciated_unicode' vs 'mysql_enable_proper_unicode')
If the warnings are annoying enough it gives the users of the
Is there anything in a db handle or statement handle one use to know
whether the running instance of DBD::MySQL will return integer columns
as IV?
I'm adding some code to a layer atop DBI which will force IV (via +=0),
but want to avoid doing that were it is not required.
The particular code
Me too!
I look forward to getting pull requests reviewed and in the driver as
well as get your UTF-8 work in per my previous email. We can use all the
help we can get.
regards,
Patrick
On 11/11/17 3:53 AM, p...@cpan.org wrote:
On Friday 10 November 2017 10:13:55 Patrick M. Galbraith
And I would suggest to disable issue tracker on github as primary bug
tracker (according to DBD::mysql documentation) is on RT and also
probably all problems are reported there. The worst thing which can be
is to have two independent bug trackers, which is current situation.
