Re: DBLOAD and DBDATE. Anything going on here?

Thanks Jonathan So the load will complete if the formats conflict, I just wont be able to search for dates after the 12th of any month. Correct? E.P.

Elvez wrote: > Thanks Jonathan > So the load will complete if the formats conflict, I just wont be able to > search for dates after the 12th of any month. > Correct? No, but it depends on the command line options you use, and so on. There are various possibilities. One of them is that you choose to start a violations table. Then your data will be loaded, but any rows where the date is not valid (eg because the month is 25 and the day is 12) will be in the violations table. If DBDATE is wrong, the accepted rows will have the day and month reversed -- so the 5th of June will be stored as the 6th of May and vice versa. With DBLOAD, you can specify that the load should ignore the first N errors and stop after that many errors. By default, I believe N is 1, though there's an outside chance it might be a small number like 5 or 10. Moral of the story -- if you were perverse enough to have unloaded the data (or otherwise generated it) with DBDATE="Y4DM.", then you had better darn well load it with DBDATE="Y4DM." set. If you were more normal and had DBDATE="dmy4/" in the environment, then you should still use DBDATE="dmy4/" when you do the load. This applies regardless of theload mechanism or program (onload/onunload don't count, and you can probably work around the issue in HPL if you really want to, but it would be easier to set DBDATE correctly). -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v1.00.PC1 -- see http://www.perl.com/CPAN #include <disclaimer.h>