Dear keepers of the modules,
As per the discussion below on the dbi-dev listserv, I will be
maintaining DBD::CSV from now on and will be uploading a new version
shortly into the ...J/JZ/JZUCKER directory.
Jeff Zucker wrote:
>
> "Wiedmann, Jochen" wrote:
> >
> > Hi, Jeff,
> >
> > Even more, I'd be happy, if you could offer to take
> > maintenance of DBD::CSV to your hands.
>
> Ok, done. I'll maintain it.
--
Jeff
--- Begin Message ---
"Wiedmann, Jochen" wrote:
>
> Hi, Jeff,
>
> > 1. The new SQL::Statement will allow manipulation of blobs, but only
> > with placeholders:
> >
> > This only works in the XS version of SQL::Statement:
> >
> > $dbh->do("INSERT INTO foo VALUES( $blob )");
> >
> > But this works in both versions:
> >
> > $dbh->do("INSERT INTO foo VALUES( ? )",undef,$blob);
>
> what's the actual difference?
In the first case SQL::Parser has to know how to parse a statement SQL
containing a blob and in the second case it can just allow
SQL::Statement to insert the blob without having to parse it within the
context of the SQL statement.
> And what does "blob" precisely
> mean in terms of SQL::Statement?
In this case it means a string that can contain unescaped single quote
characters whereas other stings can not.
> In the case of DBD::CSV, I see a good reason to drop the
> distinction between NULL and ''. In other cases this would
> be different, of course. Again, you should specify more
> details.
Ok, I'll think about it.
> DBD::CSV should run with SQL::Statement out of the box.
> So I will happily accept patches. It would be nice,
> though, if you could make the decision for "pass" or
> not based on the backing version of SQL::Statement.
Sure, that sounds good.
> Even more, I'd be happy, if you could offer to take
> maintenance of DBD::CSV to your hands.
Ok, done. I'll maintain it.
--
Jeff
--- End Message ---
