DBD::ODBC and sqlite3odbc

Hi, as requested in the unit tests, I'm here attaching my results for DBD::ODBC's t/ExecuteArray.pm tests in combination with sqlite3odbc. I *know* it is probably not very useful to use DBD::ODBC in combination with SQLite, as there is already a dedicated DBI driver, but I chose this because I

DBD::mysql 4.024 released, many fixes, especially for Windows

Patrick Galbraith has released a new version of DBD::mysql with many small fixes inside. Change log: 2013-09-17 Michiel Beijen, Patrick Galbraith, DBI/DBD community * Fix memory leak if mysql_server_prepare is enabled - RT76462 - Masahiro Chiba * Undefined $DBI::errstr on execute fail on Windows

Re: DBD::mysql 4.024 Released

Hi Robert, On Wed, Sep 25, 2013 at 2:30 AM, Robert Dodier robert.dod...@gmail.comwrote: Hi, thanks for the announcement about DBD::mysql 4.024. I tried to install it via cpan -i DBD::mysql, which apparently failed due to failed tests, so I tried it again as cpan -f -i DBD::mysql. I get the

DBD::ODBC and Unicode

Hi, I ran into this issue with DBD::ODBC; I read Martin asked about feedback on the 1.46_1 devel release. I tested my code against both versions 1.43 and 1.46_1 an the results are the same. Basically, if I do SELECT example FROM foo WHERE example LIKE 'string%'; this is OK as long as long as

Re: DBD::Oracle installation

Hi Carl, On Fri, Dec 6, 2013 at 1:06 AM, Furst, Carl carl.fu...@mlb.com wrote: However, I'm wondering why this information is not in the INSTALL file at least? Would be a good hint so people know what they would need to get going. It could be one of the reasons is there are so many

Re: Statement Handle Attribute Precision

Can you maybe create a small sample script? -- Michiel Op dinsdag 20 januari 2015 heeft Josh Nijenhuis j...@nijenhuis.ca het volgende geschreven: Using mariadb 10 series, Perl 5.18 DBI 1.623 DBD-mysql 4.20 I seem to be getting 3 byte 'PRECISION' back on the statement handle for CHAR and

DBD::mysql test release 4.030_02

IPv6 addresses in the DBI connection string. Apart from that the installation documentation has been updated and reworked. 2015-03-02 Patrick Galbraith, Michiel Beijen, DBI/DBD community (4.030_02) * Reworked installation documentation in POD. * Allow use of bracketed IPv6 addresses in connection

Re: Broken CSS onmetacpan.org

on your page but not others such as DateTime. >> >> I suspect they have a missing directive on your page or it is some >> corner-case "bug" in the obfuscated JavaScript. >> >> Best Regards >> >> Geoff >> >> >> >> >>

Re: Broken CSS onmetacpan.org

This is a metacpan problem, I reported it at https://github.com/CPAN-API/metacpan-web/issues/1604#issuecomment-148427917 By the way; for me it *seems* to work now. -- Michiel On Thu, Oct 15, 2015 at 11:07 AM, Geoff Collis via dbi-users < dbi-users@perl.org> wrote: > FYI: your CSS appears to be

MySQL issue with InsertID

Hi all, I wanted to point out that I have reported an issue with the latest 'dev' release of MySQL and DBD::mysql concerning mysql_insertid http://bugs.mysql.com/bug.php?id=78778 It's been confirmed as an issue in the above bug report (by Oracle and/or by someone operating under the handle

Re: Broken CSS onmetacpan.org

ari, IE11 all > OK): > > > > > Still have the issue, see screenshot. > > - Geoff > > > On Thursday, October 15, 2015 7:33 PM, Michiel Beijen > <michiel.bei...@gmail.com> wrote: > > > This is a metacpan problem, I reported it at > https://github.com

New test release DBD::mysql 4.033_01 available - ssl by default?

feedback (+1's, remarks or objections) would be appreciated! ** Changelog for this development release ** 2015-12-15 Patrick Galbraith, Michiel Beijen, DBI/DBD community (4.033_01) * Raise minimum DBI version to 1.609 (from 2009!) in order to make tests pass on RHEL5. * Add explicit

SECURITY RELEASE - Buffer overflow in DBD::mysql perl library

soon. Many thanks to Pali Rohár for discovering and fixing the vulnerability. -- The DBD::mysql maintainers, Patrick Galbraith Michiel Beijen

Security release - use after free in DBD::mysql when using prepared statements

Users of DBD::mysql using prepared statements are advised to patch their installations as soon as possible. Many thanks to Pali Rohár for discovering and fixing the vulnerability. -- The DBD::mysql maintainers, Patrick Galbraith Michiel Beijen

DBD::mysql unicode bug fixes in new development release

Hi, (if you rather read a website than plain text, this is also on my site: https://huntingbears.nl/2016/12/14/dbdmysql-all-your-utf-8-bugs-are-belong-to-us/) After a couple of years of more or less “maintenance mode” on DBD::mysql – we had a hand full of people contributing occasional fixes

DBD::mysql new development release, test our unicode improvements!

(if you rather read a website than plain text, this is also on my site: https://huntingbears.nl/2017/03/02/dbdmysql-even-more-utf8-issues-fixed-super-ci/) In my previous mail (https://huntingbears.nl/2016/12/14/dbdmysql-all-your-utf-8-bugs-are-belong-to-us/) I explained how many utf-8 related

Re: DBD::mysql next steps

Hi Pali! On Thu, Nov 16, 2017 at 12:49 PM, wrote: > Hi! And what are you going to do with all commits which you reverted in > 4.043 version? As I remember, months ago you wrote that you reapply > fixes, but nothing happened. Instead you started merging conflicting > new pull

Re: Bugtracker DBD::mysql

On Tue, Nov 14, 2017 at 11:07 AM, wrote: > Hi! As there are only few tickets on github, it would be easier to > disable creating new tickets on github and those few which are not > resolved yet either move on RT or (if github allows it; which I believe > yet) continue to exists.

Bugtracker DBD::mysql

Hi Pali, On Mon, Nov 13, 2017 at 6:18 PM, wrote: > 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

Re: Bugtracker DBD::mysql

On Tue, Nov 14, 2017 at 5:40 PM, Dan Book wrote: > I also prefer github but of course it's mainly up to what is easiest for the > maintainers. Here is a script for migrating tickets if it's not what you > already tried: https://metacpan.org/pod/RTx::ToGitHub Actually, that is

Re: DBD::mysql path forward

I think we have not decided how we should fix the unicode issues. Previously in this thread, it seemed to be pali and Dan Book had other ideas about this than most others. I wrote on this topic earlier to pali: On Wed, Sep 13, 2017 at 9:21 AM, wrote: > I would suggest to

Re: DBD::mysql path forward

Hi Darren, Dan, On Fri, Nov 10, 2017 at 7:16 AM, Darren Duncan wrote: > On 2017-11-09 8:32 AM, Dan Book wrote: >> >> It seems to me like the remaining option that can make everyone "happy" is >> the >> previously-suggested option of maintaining a legacy branch and doing