On Tue, Aug 29, 2017 at 3:36 AM, wrote:
> 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
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 PRs
>
> How might we allow people time to test the fixes to give them time? Just
> have them use the fork, I would assume?
>
> Regards,
>
> Patrick
>
On Tue, Sep 12, 2017 at 11: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
>> PRs
>>
>> How might we allow peo
On Wed, Sep 13, 2017 at 3:53 AM, Peter Rabbitson wrote:
> On 09/12/2017 07:12 PM, p...@cpan.org wrote:
>
>> 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 Per
How can we proceed from here?
-Dan
On Mon, Sep 18, 2017 at 1:17 PM, Patrick M. Galbraith wrote:
> Pali,
>
> Great! Now we can start moving forward.
>
> Sorry if my responses have been intermittent - first week at new job.
>
> Regards,
>
> Patrick
> On 9/16/17 4:35 AM, p...@cpan.org wrote:
>
> I
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
new development (reinstating 4.042) in another branch which will be
released as a new distribution, like DBD::mysql2, by the same maintainers.
(I would
On Fri, Nov 10, 2017 at 8:43 PM, Noel Butler wrote:
>
> Given that things are only ever going to move forward with my/maria-sql
> would it not be better to enable this by default, and have a "disable"
> setting for those who want to run something of antiques?
>
> Because in years to come there wil
On Tue, Nov 14, 2017 at 8:34 AM, Michiel Beijen
wrote:
> 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 allo
Also make sure you set AutoInactiveDestroy, which would be default if not
for back compat, otherwise a fork that doesn't even use the handle may
close your connections.
Making sure connections are specific to one process can be tedious,
especially when you are not controlling the processes, one ea
On Tue, Aug 17, 2021 at 3:42 AM Simon Cruickshank <
simon.cruicksh...@gmail.com> wrote:
> I use perl CGI::Session on a Debian buster box, after upgrading to
> Bullseye the website barfs with message :-
>
> DBD::mysql::db do failed: Incorrect string value:
> '\xF9\x08a\x00\x00\x00...' for column `w
On Mon, Dec 16, 2024 at 5:13 PM Shaomei Liu
wrote:
> Hello,
> very happy to find this mailing list as it is my last resort!!
> I have a project which uses DBI to write to postgres DB.
> after upgrading from RHEL7 to RHEL8, the utf-8 character is not displayed
> properly in the DB. DB has correct
Indeed, how strings work has not changed, but DBD::Pg's interpretation of
your strings probably did; the new behavior is more "correct" and now that
you are sending it decoded Unicode characters you may avoid
other mysterious issues. (Note that DBI itself does not handle strings, it
just provides t
12 matches
Mail list logo
