Re: DBD::MySQL upstream change

Hi Pali,

Thanks for the clarification.

On 31/03/2024 21:42, [email protected] wrote:

> On Sunday 31 March 2024 10:03:33 Florian Smeets wrote:

Hrmmm did not see Florian's reply to me, so following is directed to 
Florian.

(ohh pssst you can't use that TLD to mail me direct, and I guess the 
list is set to not send list copy if direct send, I'll look at sorting 
that)

>> My mail contained two links which you stripped that explain issues 
>> people
>> saw when migrating to DBD:MariaDB.
>> 
>> https://blogs.perl.org/users/grinnz/2023/12/migrating-from-dbdmysql-to-dbdmariadb.html
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277889#c16
>> 
>> I haven't analyzed it in that much detail to say if it will work in 
>> most
>> cases or just in a lot of cases, all I'm saying is that some care 
>> needs to
>> be taken as there are subtle differences, so not a 100% drop-in 
>> replacement.
>> 
>> Florian

First, I always believe in trimming posts, don't see the need to keep 
reposting links or text not needed over and over, it annoys many to no 
end those who just hit reply reply reply and soon enough you have a post 
thats 150k in size for an extra 6 lines on top of the 5k OP.

Secondly, I admit not reading Grinz's blog, however at the time the 
second link (since you are from freebsd I chose to read that one) timed 
out.

Thirdly as I said, in our environment, and in several others (I too was 
initially cautious before jumping head on in back in the day, and IRC 
advice from other ISP admins was yeah it's a drop in replacement) they 
just moved their DBI connect from mysql to MariaDB and everything 
worked,  which is what I ended up doing, and yes everything worked no 
errors, so in many environments, yes it is a complete drop in 
replacement, but I note as Pali points out below there are edge cases 
where this is not so.

> At a fork time there were fixed lot of bugs from DBD::mysql bugtracker
> which users reported. I think there were 3 big changes which may cause
> incompatibility with DBD::mysql.
> 
> 1) Renaming options. All DBI options which starts with "mysql_*" are
> DBD::mysql driver specific and so DBD::MariaDB cannot provide them. It
> has to use "mariadb_*" prefix. So if application uses driver specific
> mysql_* options they have to be renamed.

...

-- 
Regards,
Noel Butler