On Mo, 1999-07-26 23:05:37 +0300, Sinisa Milivojevic wrote:
> The only way, I think, warnings could be made fully visible, is to
> make LOAD DATA on a client's side and fully interactive. I mean FULLY
> interactive. But then, it would not be fast !!
>
> May be I should put it in a TODO for sqlclient ??
I could imagine having a new pseudo table ERRORS and doing SELECT *
FROM ERRORS would give all the errors and warnings.
But I've to admit that I know nothing yet about the internals of MySQL
and how difficult this would be to accomplish (maybe the warnings
aren't available even internally ...) and if it's worth the effort.
For the time being an extension to sqlclient would be nice: if you're
desperately searching for malformed fields in your import data, speed
is secondary if only you can _find_ the culprits ;-)
Regards,
Martin
--
Martin Ramsch <m.ramsch@stripped> <URL: http://home.pages.de/~ramsch/ >
PGP KeyID=0xE8EF4F75 FiPr=52 44 5E F3 B0 B1 38 26 E4 EC 80 58 7B 31 3A D7
