MSQLB Problem running mysqlimport with TIMESTAMP column type

Hi!

>>>>> "taa" == taa writes:

taa> Thu 09-19-02 10:50 pm
taa> Summary: A warning is generated when attempting to import a
taa> TIMESTAMP column of zero or zeroes. SELECT INTO OUTFILE
taa> gives identical content as the import file.



taa> How-To-Repeat:

taa> 1. Create file C:\TEMP\BUG.DEF containing the following:
taa> --------------------------------------------------------



taa> 7. The questions I have are: Why is a warning being generated and what
taa> is the warning?

MySQL always generate a warning when one sets a timestamp to 0. I
have now fixed this in the 4.0 source tree so that we don't get a
warnings when we set a timestamp to a string if 0.

taa> It is my understanding that because no log file is generated from
taa> mysqlimport, the only way to troubleshoot warnings is to export
taa> the file and do a comparision to see what is different. In this
taa> case, the import and export files are identical.

For the moment this is true.
In the MySQL 4.1 source tree we already have a warning system, which
we will extend to make things like this easy to find.

Regards,
Monty

--
For technical support contracts, goto https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Michael Widenius
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, CTO
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
<___/ www.mysql.com


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12598@lists.mysql.com
To unsubscribe, e-mail