http://qs321.pair.com?node_id=404814


in reply to Data interpretation

  1. For the year (2003), sort by month.
  2. For one month (say Jan), get the product released for every day.
  3. Automate that data to get into charts. What is required is a chart for every day for one month. For that day, I would need to show what products are released.

Sounds like a problem for a (relational) database.

--
Yours in pedantry,
F o x t r o t U n i f o r m
"Anything you put in comments is not tested and easily goes out of date." -- tye

Replies are listed 'Best First'.
Re^2: Data interpretation
by rupesh (Hermit) on Nov 03, 2004 at 04:44 UTC

    An RDBMS would be simple and easier to manage I agree. The issue is that the data is in the form of .csv.
    Rupesh.
[reply]

      You might find DBD::CSV handy, then.

      --
      Yours in pedantry,
      F o x t r o t U n i f o r m
      "Anything you put in comments is not tested and easily goes out of date." -- tye

[reply]
      So use, DBD::CSV which will allow you to use DBI and SQL on your files and treat them like an RDBMS.
[reply]
      So what? Load it into a database. I'm going to assume that this is data that will not change, as you mention it's sales data. So, you're probably going to want this in a database anyways.

      Being right, does not endow the right to be rude; politeness costs nothing.
      Being unknowing, is not the same as being stupid.
      Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
      Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

[reply]
      You mean, there's still a database out there that isn't able to import from the CSV file? Quick! Call the Smithsonian!
[reply]

In Section Seekers of Perl Wisdom