Well then, why not write a script that doesn't use DBI at all, but simply reads the original tab-delimited text file and writes a "fixed" version of it that mysql's import tool will accept? It should end up being the same amount of programming work or less, compared to doing the job with DBI -- you still have to understand what the problems are with the original data, and how to fix them (unless you end up taking short cuts in the DBI approach, either intentionally or accidentally, that result in the "large number of errors" being ignored rather than fixed, but you probably don't want that sort of short cut). And of course the script without DBI and inserts will run a lot faster than the DBI approach.
I think your reference to INFILE and my reference to LOAD DATA are actually referring to the same process. I know that when you run mysql directly, you can issue a LOAD DATA command as an sql statement, but I don't know for sure if this can be used via DBI -- it's worth a try.
In reply to Re^4: Looking for elegant solution to dbi coding problem
by graff
in thread Looking for elegant solution to dbi coding problem
by Commander Salamander
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |