Re: Re: Re: Re: DBD::CSV limitation versus aging/unmaintained modules (lazy)

[tilly]

But you have not actually solved the problem from your side. You have just hidden it - guaranteed that if any fields anywhere have a comma in it, then you will silently give wrong results.

I would suggest having your code at least put in some highly visible check for, for instance, an unexpected number of fields. And escalate the formatting issue a level or two. Because if their output doesn't correctly format CSV, then at some point there is nothing that you can do to work around the breakage.