Re: any known DBD::pg change caused this utf8 issue?
Greg Sabino Mullane <[email protected]> Thu, 19 Dec 2024 17:04:11 -0500
| Newsgroups | gmane.comp.db.postgresql.dbdpg |
|---|---|
| Message-ID | <CAKAnmmKbM0ZhXV2kc0XeED=g9UeuQ3u9zeduqeEq0vJW16VA2w@mail.gmail.com> |
--000000000000fa875d0629a6b7e3 Content-Type: text/plain; charset="UTF-8" > > perl -MDBD::Pg -e'print $DBD::Pg::VERSION' > EL8 3.7.4 > EL7 2.19.3 Yep, that explains it. Version 2.19.3 was released in 2012. The next version, 3.0.0, made some major changes to the handling of UTF-8. As a matter of fact, that was one of the reasons for making a major bump to 3.x rather than releasing a 2.x Both of those versions were released over a decade ago! Version 3.7.4 was released in 2018. It's generally best to use the "cpanm" program or similar to install a newer version of DBI, DBD::Pg, etc. rather than relying on the underlying OS. Cheers, Greg --000000000000fa875d0629a6b7e3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px = 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">perl -MD= BD::Pg -e'print $DBD::Pg::VERSION'<br>EL8 3.7.4<br>EL7 2.19.3</bloc= kquote><div><br></div>Yep, that explains it. Version 2.19.3 was released in= 2012. The next version, 3.0.0, made some major changes to the handling of = UTF-8. As a matter of fact, that was one of the reasons for making a major = bump to 3.x rather than releasing a 2.x<div><br></div><div>Both of those ve= rsions were released over a decade ago! Version=C2=A03.7.4 was released in = 2018.<div><br></div><div>It's generally best to use the "cpanm&quo= t; program or similar to install a newer version of DBI, DBD::Pg, etc. rath= er than relying on the underlying OS.</div><div><br></div><div>Cheers,</div= ><div>Greg</div><div><br></div></div></div> --000000000000fa875d0629a6b7e3--