Hmm I thought that I already found where the problem is - record 3964, this is the one after which DBD::CSV stops noticing more records.
I just can find what exactly DBD::CSV finds wrong about that record/line, and more importantly - why doesn't it emit any kind of warning when it finds those 'corrupted' lines.
In reply to Re: Re: DBD::CSV limitation versus aging/unmaintained modules (lazy)
by Eyck
in thread DBD::CSV limitation versus aging/unmaintained modules
by Eyck
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |