As a side note, I have in the past thought a HandleWarn option may be
useful, for instance to log warnings from the database or other custom
behavior. It could also be used to throw exceptions.
-Dan
On Thu, Jan 17, 2019 at 4:03 AM wrote:
> Hello!
>
> What do you think about adding a new attribu
While I'm a staunch opponent of fatal warnings in general, and I believe
Pali has voiced concern with them as well, this is somewhat unrelated as it
has nothing to do with the core warnings pragma and categories, and is
simply an *option* to cause DBI to exhibit different behavior which it
currentl
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
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
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
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
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 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, 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