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 add
it
currently cannot. As such I think it's a fine idea.
-Dan
On Thu, Jan 17, 2019 at 6:20 PM Alexander Hartmaier
wrote:
> I didn‘t want to start a discussion about deprecation because I know the
> opinion about that for most Perl 5 developers.
>
> But strictures and its use in Moo showed tha
github but of course it's mainly up to what is easiest for
the maintainers. Here is a script for migrating tickets if it's not what
you already tried: https://metacpan.org/pod/RTx::ToGitHub
-Dan
ity should not be fractured; the current module will simply
be abandoned for future development, all support and maintenance will move
to the new one. Patrick and Michiel, what do you think?
-Dan
How can we proceed from here?
-Dan
On Mon, Sep 18, 2017 at 1:17 PM, Patrick M. Galbraith <p...@patg.net> wrote:
> Pali,
>
> Great! Now we can start moving forward.
>
> Sorry if my responses have been intermittent - first week at new job.
>
> Regards,
>
>
script side-steps showcasing the treatment of BLOB/BYTEA columns,
> which was one of the main ( albeit not the only ) reason the userbase lost
> data.
>
> Please extend the script with a BLOB/BYTEA test.
>
I'm not sure how to usefully make such a script, since correct insertion of
BLOB data (binding with the SQL_BLOB type or similar) would work correctly
both before and after the fix.
-Dan
On Tue, Sep 12, 2017 at 11:54 AM, Dan Book <gri...@gmail.com> wrote:
> On Tue, Sep 12, 2017 at 11:04 AM, Patrick M. Galbraith <p...@patg.net>
> wrote:
>
>> Pali,
>>
>> Yes, I agree, we'll have to create a fork pre revert and stop accepting
>> PRs
be very clear if this is your intended approach, as this
is what led to many people corrupting data as they send blobs to mysql with
the same mysql_enable_utf8 option, and expect them to accidentally not get
encoded.
-Dan
st the new MariaDB C-client?
> > >
>
My reply yesterday seems to not have gone through, so I am replying again
here.
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 (
https://github.com/perl5-dbi/DBD-mysql/compare/4.041...4.042 ) as well as
re-adding a correct utf8 encoding option, as it is still necessary to fix
this broken behavior one way or another. Since nothing has happened,
forking may be the only reasonable option. We are currently version pinned
to 4.042 as "upgrading" to 4.043 would be a massive regression in our
codebase.
-Dan
Branch: refs/heads/master
Home: https://github.com/perl5-dbi/dbi
Commit: 49b330e4d1d7983813084d661b5b2990ea63874f
https://github.com/perl5-dbi/dbi/commit/49b330e4d1d7983813084d661b5b2990ea63874f
Author: Dan McGee <dmc...@barracuda.com>
Date: 2016-04-21 (Thu, 21 Ap
,
-Dan
Can you please post the Perl code you're using (or at least the
section relevant to the prepare_cached() method and failure) so we can
give you a little more help?
Thanks,
Dan
On 10/31/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi, I am using a perl script to load data in a DB2 database
want to issue a global
rollback or commit?
Perhaps (probably) I'm suffering from a limited imagination here, but
it seems like you would want to rollback or commit on a connection by
connection basis.
Dan
.
Dan
--
Dan Frankowski mailto:[EMAIL PROTECTED]
-Original Message-
From: Jeff Urlwin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 16, 2001 3:20 PM
To: Frankowski, Dan; 'Jeff Urlwin'
Cc: [EMAIL PROTECTED]
Subject: RE: bind_param_array for SQLBulkOperation ?
What database
14 matches
Mail list logo
