Re: DBD::mysql path forward

2017-09-14 Thread pali
On Thursday 14 September 2017 08:21:42 H.Merijn Brand wrote: > On Wed, 13 Sep 2017 13:27:58 -0700, Darren Duncan > wrote: > > > On 2017-09-13 12:58 PM, Dan Book wrote: > > > On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson wrote: > > > > > > On 09/12/2017 07:12 PM,

Re: DBD::mysql path forward

2017-09-16 Thread pali
at > >> with a commit to master that changes the DBD::mysql version to > >> 5.0. > > > > If everybody agree with this step, I can prepare pull request which > > revert tree to this state, plus re-apply/rebase commits which were > > newly accepted. I prepare

Re: DBD::mysql path forward

2017-10-04 Thread pali
On Tuesday 26 September 2017 14:20:33 Night Light wrote: > That's a nifty function. Good to know that it can be reversed. UTF-8 encode is a function which for any number from the range 0..1114111 assign unique sequence of the numbers 0..255. Therefore this function has a well defined inverse -

Re: DBD::mysql path forward

2017-10-04 Thread pali
On Tuesday 26 September 2017 14:20:33 Night Light wrote: > I noticed that it was mentioned in DBD::mysql # 117 that DBD::mysql does > know that a column in a returned resultset is a BLOB. For returned values via MySQL protocol, there are two different and independent things: SQL type and

Re: Fork DBD::mysql

2017-10-13 Thread pali
On Wednesday 11 October 2017 15:09:49 Steven Lembark wrote: > > > It is not as easy as it could appear. And also in some cases migration > > from MySQL/MariaDB to Pg could be problematic from performance point of > > view. One Pg developer already told us that for our use case is really > > MySQL

Re: DBD::mysql path forward

2017-09-13 Thread pali
; > Thank you for the great discussion! > > Patrick > > On 9/12/17 2:05 PM, p...@cpan.org wrote: > >On Tuesday 12 September 2017 19:00:59 Darren Duncan wrote: > >>On 2017-09-12 8:54 AM, Dan Book wrote: > >>>On Tue, Sep 12, 2017 at 11:04 AM, Patrick M. Galbraith wrot

Re: DBD::mysql path forward

2017-09-13 Thread pali
On Tuesday 12 September 2017 11:32:36 Darren Duncan wrote: > On 2017-09-12 11:05 AM, p...@cpan.org wrote: > >On Tuesday 12 September 2017 19:00:59 Darren Duncan wrote: > >>I strongly recommend that another thing happen, which is > >>re-versioning DBD::mysql to 5.0. > >> > >>1. From now on,

Re: DBD::mysql path forward

2017-09-12 Thread pali
On Tuesday 12 September 2017 05:40:31 Patrick M. Galbraith wrote: > Hi all, > > After talking to Pali and looking at how other drivers have handled the > issue, the best way forward will be to deal with solving the UTF-8 issue > correctly as was attempted in May. This will be a p

Re: DBD::mysql path forward

2017-09-12 Thread pali
On Tuesday 12 September 2017 19:00:59 Darren Duncan wrote: > On 2017-09-12 8:54 AM, Dan Book wrote: > > On Tue, Sep 12, 2017 at 11:04 AM, Patrick M. Galbraith wrote: > > Pali, > > Yes, I agree, we'll have to create a fork pre revert and stop > > accepting PR

Re: DBD::mysql path forward

2017-09-12 Thread pali
eases like it was between 4.041 and 4.042. Any comments from other people about this idea? On Tuesday 12 September 2017 17:04:18 Patrick M. Galbraith wrote: > Pali, > > Yes, I agree, we'll have to create a fork pre revert and stop > accepting PRs > > How might we allow people time to

Re: DBD::mysql path forward

2017-09-12 Thread pali
On Tuesday 12 September 2017 12:27:25 p...@cpan.org wrote: > To prove fact that other DBI drivers (e.g. Pg or SQLite) had fixed > similar/same UTF-8 issue as MySQL has and behave Perl-correctly, I > would provide test cases so you would see difference between Pg, > SQLite and mysql DBI drivers.

Re: DBD::mysql path forward

2017-09-24 Thread pali
Hello, may I ask how this situation differs from upgrading DBD::Pg to version 3.3.0 or DBD::SQLite to version 1.43_04? What you are writing there basically affects also DBD::SQLite... And version 1.43_04 was already released... On Tuesday 19 September 2017 14:46:09 Night Light wrote: > Dear

Fork DBD::mysql

2017-08-28 Thread pali
Hello, 2 months passed since two security problems related to DBD::mysql were reported, namely CVE-2017-10789 and CVE-2017-10788. Looking at the DBD::mysql github project page and RT bugtracker, it can be seen that nothing has happened for 2 months. Some people are asking or waiting for reported

Re: [External] Fork DBD::mysql

2017-08-29 Thread pali
Then users of MySQL would stay with DBD::mysql and they would not have fixed DBD driver. We were thinking about choosing DBD::mariadb name for our fork. But without dropping MySQL support, so also MySQL users could benefit from it. On Monday 28 August 2017 18:08:20 Daniël van Eeden wrote: > What

Re: Fork DBD::mysql

2017-09-01 Thread pali
first email in this thread. > Author: Michiel Beijen <michiel.bei...@gmail.com> 2017-06-29 11:25:48 > Committer: Michiel Beijen <michiel.bei...@gmail.com> 2017-06-29 11:30:07 > Tags: 4.043 > Parent: 1ece6b4b8630a1cf348373aa41cbe5f748dcd62a (Merge pull request #137 > from pali/versions) > Branch: remotes/origin/master > Follows: 4.042 > Precedes: > > New version 4.043 - the same as 4.041

Re: Fork DBD::mysql

2017-09-02 Thread pali
On Friday 01 September 2017 17:01:49 Patrick M. Galbraith wrote: > Hi Pali, > > I would very much like to address these issues and fix the UTF issue you so > kindly had a patch for that people had problems with and do so in a way that > doesn't require forking. I'm very sorry

Re: Fork DBD::mysql

2017-08-29 Thread pali
On Monday 28 August 2017 09:19:46 Darren Duncan wrote: > While a fork may be the best short term fix, as keeping up with security > issues is important, I honestly believe that the best fix is to migrate to > Postgres as soon as you can. It is not as easy as it could appear. And also in some

Re: Fork DBD::mysql

2017-09-01 Thread pali
On Tuesday 29 August 2017 22:08:09 Dan Book wrote: > Though the reversion was made with good intentions of preserving back > compat in the short term, it was accompanied by a promise of reapplying the > many important fixes that were reverted ( >

Re: DBD::mysql path forward

2017-11-10 Thread pali
I do not understand what (and how) your proposal with =2 solve. Probably nothing and people would again start after final release again complaining... On Friday 10 November 2017 09:24:35 Night Light wrote: > Forking would take away my concerns (thank you all for suggesting that) but > one thing

Re: DBD::mysql path forward

2017-11-10 Thread pali
On Friday 10 November 2017 07:59:05 Michiel Beijen wrote: > I'll stick with my earlier proposal - I'll propose to go back to the > *current* latest DBD::mysql release which does not break backcompat > for our users; add the patches that we discarded when we rolled back > one by one, such as

Re: DBD::mysql next steps

2017-11-16 Thread pali
On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote: > Greetings all! > > Michiel and I have been talking, weighing options of what course to take in > dealing with moving forward-- with the goal of both offering both stability > and the choice to have the latest functionality and bug

Re: DBD::mysql path forward

2017-11-10 Thread pali
Technical: Reason why it does not help nor solve the main problem: Due to internals, DBD::mysql pseudo-randomly decide if input bind variable is encoded to UTF-8 or not. And do it independently of how is option enable_utf8 configured. As we know there are applications which misuse this internal.

Re: DBD::mysql path forward

2017-11-10 Thread pali
On Friday 10 November 2017 10:09:59 demerphq wrote: > Pali is there a concise summary of what we are arguing about here? Short summary: 1. There are applications which misuse perl and DBD::mysql internals to pass blob or utf-8 text data from perl to MySQL database. We were not aw

Re: Bugtracker DBD::mysql

2017-11-14 Thread pali
On Tuesday 14 November 2017 10:56:58 Michiel Beijen wrote: > Hi Pali, > > On Mon, Nov 13, 2017 at 6:18 PM, <p...@cpan.org> wrote: > > And I would suggest to disable issue tracker on github as primary bug > > tracker (according to DBD::mysql documentation) is on R

Re: DBD::mysql next steps

2017-11-13 Thread pali
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.

Re: DBD::mysql path forward

2017-11-10 Thread pali
D::mysql (as libmysqlclient application) stopped working, > > because is misusing internals of C structures? > > Pali, I wanted to give you some feedback on this thread. I have been > monitoring this discussion for some time. My $workplace probably has > one of the largest

Re: DBD::mysql next steps

2017-11-11 Thread pali
On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote: > Greetings all! > > Michiel and I have been talking, weighing options of what course to take in > dealing with moving forward-- with the goal of both offering both stability > and the choice to have the latest functionality and bug

Re: DBD::mysql path forward

2017-11-09 Thread pali
odule from cpan or external source not related to DBD::mysql. > > > > Pali. This "argument" applies to a large portion of CPAN. All JSON variants, > various web frameworks, even things as mundane as math libraries: > https://rt.cpan.org/Public/Bug/Display.htm

Re: DBD::mysql path forward

2017-11-09 Thread pali
Hi! I'm responding below. On Tuesday 07 November 2017 13:19:23 Darren Duncan wrote: > Patrick and Pali, each of you please respond to the lists to confirm that > what I say below is what you also understand is the primary plan, and if > not, then say why not; in prior discussion I r

Re: DBD::mysql path forward

2017-11-09 Thread pali
On Thursday 09 November 2017 13:01:19 H.Merijn Brand wrote: > On Thu, 9 Nov 2017 12:32:00 +0100, p...@cpan.org wrote: > > > > Satisfy the above - and you do get the privilege of being a maintainer > > > of a central module with 15+ years of history. > > > > Why should I be interested in

Re: DBD::mysql path forward

2017-11-09 Thread pali
; >and the users want now, or will need in the near future, to build with > >latest, stable and recommended versions of MariaDB and MySQL. > > Which is a great thing to want. I want this too. This is not what the thread > is about. > > The problem stems from Pali ma

Re: Extend API for last_insert_id

2018-05-04 Thread pali
Hello, do you have any opinion or comments? Tim, you as a DBI maintainer, what do you think about those ideas? On Friday 27 April 2018 16:03:59 p...@cpan.org wrote: > Hello, > > I would like to propose two new changes to DBI which extends > last_insert_id API. > > First one: Allow to call

Re: Extend API for last_insert_id

2018-05-16 Thread pali
> That seems fine. I'd write the fallback code like this: > > sub last_insert_id { return shift->{Database}->last_insert_id(@_) } Changed. And now I created a pull request with these changes: https://github.com/perl5-dbi/dbi/pull/64 > Thanks Pali. > > Tim.

DBD::MariaDB beta 0.90_01 released on CPAN

2018-06-27 Thread pali
Hello, I would like to announce that after few months of DBD::MariaDB development, beta version 0.90_01 of DBD::MariaDB is now on CPAN: https://metacpan.org/release/PALI/DBD-MariaDB-0.90_01 DBD::MariaDB is a DBI driver for connecting to the MariaDB or the MySQL database. It is a fork

New DBI driver DBD::MariaDB

2018-01-23 Thread pali
Hello, I would like to announce a new DBI driver for MariaDB and MySQL databases. As stated in the email [1] which I sent to this mailing list about a half year ago, we in the GoodData company decided to create a fork of the old DBD::mysql driver under the name DBD::MariaDB. The source code of

DBD::MariaDB 1.00 released on CPAN

2018-07-12 Thread pali
Hello! I would like to announce public release of the DBD::MariaDB 1.00. Now it is available on CPAN and can be installed directly via cpan client. https://metacpan.org/release/PALI/DBD-MariaDB-1.00 There is a problem with perl mailing lists and perl email servers, therefore it is possible

Re: New DBI driver DBD::MariaDB

2018-01-23 Thread pali
On Tuesday 23 January 2018 11:14:13 p...@cpan.org wrote: > * Better compatibility with the MariaDB client library Basic unit tests passed on Travis with last MySQL versions 5.5.58, 5.6.38, 5.7.20, 8.0.3 and MariaDB versions 5.5.58, 10.0.33, 10.1.30, 10.2.12, 10.3.3. Also with MariaDB C/Connector

Re: Generic way of fetching a list of databases

2018-11-16 Thread pali
On Friday 16 November 2018 13:09:21 Daniel Kasak wrote: > Hi all. > > I have a project that has to support pretty much every major database > around, plus a number of more esoteric "big data" platforms as well. Until > now, I've had a bunch of methods, implementing fetching databases, schemas, >

Re: Tim Bunce - RE: DBD-DBI Insert Binary Files and using Perl modules in cPanel environment

2018-09-28 Thread pali
Hi! I do not know if it helps you, but processing binary data with MySQL or MariaDB server and Perl's DBI can be tricky due to limitation of MySQL protocol. Some details I wrote to the DBD::MariaDB documentation: https://metacpan.org/pod/DBD::MariaDB#Working-with-binary-data

Re: Wierd issue with printf and DBD::Pg

2018-10-01 Thread pali
On Monday 01 October 2018 11:13:48 Mike Martin wrote: > HI > If I use printf to round a numeric value before inserting into postgres > table it is altered to 1 rather than the value when it is put into a table Hi! Function printf takes format string with parameters and then it prints to the

Re: Generic way of fetching a list of databases

2018-11-18 Thread pali
clientversion => 80013, > data_sources => [ > "DBI:MariaDB:information_schema", > "DBI:MariaDB:mysql", > "DBI:MariaDB:performance_schema", > "DBI:MariaDB:sys", > ], > dbd => "DBD::MariaDB", > dbd_version =>

Re: macOS Mojave "Can't link/include C library ' ', aborting"

2019-01-16 Thread pali
On Wednesday 16 January 2019 17:59:07 James Brown via dbi-users wrote: > > On 16 Jan 2019, at 5:48 pm, Daniël van Eeden > > wrote: > > > > The --libs part of that looks wrong. > > I would expect something like "... -lmysqlclient -lssl -lcrypto”, not a -l > >

DBD::MariaDB 1.10 released on CPAN

2018-12-05 Thread pali
Hello! I would like to announce that DBD::MariaDB 1.10 was released on CPAN. https://metacpan.org/release/PALI/DBD-MariaDB-1.10 DBD::MariaDB is DBI driver for connecting to MariaDB and MySQL databases. It is a fork of DBD::mysql driver which aims to work correctly with Unicode and to have

DBD::MariaDB 1.21

2019-02-27 Thread pali
Hello! New version of DBD::MariaDB 1.21 is now on CPAN: https://metacpan.org/release/PALI/DBD-MariaDB-1.21 DBD::MariaDB is DBI driver for connecting to MariaDB and MySQL databases. It is a fork of DBD::mysql driver which aims to work correctly with Unicode and to have a better support

Re: Translate between DBI and SQL

2019-02-11 Thread pali
On Friday 08 February 2019 22:37:17 Mike Martin wrote: > Has anyone done any work on converting SQL queries between RDBMS and perl? > > My particular interest is DBD::Pg but anything would be of use > > It would be very useful when I am testing complex SQL, it's very easy to > miss a \ or quote

Re: Strange issue with inserting varchar2()

2021-05-27 Thread pali
On Thursday 27 May 2021 23:35:32 Bruce Johnson wrote: > use bytes; $string=substr($orig,0,4000); Hello! This is really suspicious. See **BOLD** description of 'bytes' module: **Use of this module for anything other than debugging purposes is strongly discouraged.** **If you feel that the

DBD::MariaDB 1.23

2023-09-10 Thread pali
Hello, New version of DBD::MariaDB 1.23 is now on CPAN: https://metacpan.org/release/PALI/DBD-MariaDB-1.23 DBD::MariaDB is DBI driver for connecting to MariaDB and MySQL databases. It is a fork of DBD::mysql driver which aims to work correctly with Unicode and to have a better support