Disclaimer: Whatever errors I find may be unrelated to the problem itself as I repeatedly got distracted while writing this comment...

- (A trait of senior monks that's rubbed off on me): use strict - it helps...

- Shouldn't

for ($ii = @time[0]; $ii <= @time[$#time]; $ii++)

[download]
be using $time[0] and $time[$#time]? There are also other lines using that notation...

- In your "Code with DBI" make PrintError=>1 and redirect the output for late night reading ;)

- Check those output files to make sure that there are no "character combinations" that have a special meaning in SQL... It could be where you're losing the data...

--------------------------------
An idea is not responsible for the people who believe in it...

In reply to Re^3: DBI/load data infile issue by bofh_of_oz
in thread DBI/load data infile issue by jimbus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.