Bryan Harris <[EMAIL PROTECTED]> wrote:
>>> I'm pretty new to MySQL, but I already like it. Kudos to the developers!
>>>
>>> I recently did a mysqlimport on a few data files, and it came back with over
>>> 4000 warnings. How can I actually see what the warnings were? I'm still
>>> not sure what
>> I'm pretty new to MySQL, but I already like it. Kudos to the developers!
>>
>> I recently did a mysqlimport on a few data files, and it came back with over
>> 4000 warnings. How can I actually see what the warnings were? I'm still
>> not sure what it was upset about...
>
> You can't.
> Fr
Bryan Harris <[EMAIL PROTECTED]> wrote:
>
> I'm pretty new to MySQL, but I already like it. Kudos to the developers!
>
> I recently did a mysqlimport on a few data files, and it came back with over
> 4000 warnings. How can I actually see what the warnings were? I'm still
> not sure what it was
On Wednesday 26 February 2003 02:40, Robert Mark Bram wrote:
> mysql>LOAD DATA LOCAL
> ->INFILE
> "/Rob/architecturalScreens/prototype/v1/database/insertPart.dat"
> ->INTO TABLE part;
> Query OK, 496 rows affected (0.08 sec)
> Records: 496 Deleted: 0 Skipped: 0 Warnings: 149
