1 Reply Latest reply: Aug 30, 2013 10:42 AM by Friedrich Hofmann RSS

    Conflict of date format combined with the holiday-effect...

    Friedrich Hofmann

      Hi,

       

      I am facing an issue concerning date formats:

      - Just before I went on holiday for three weeks, I set up a "historical qvd" that stores one value per day, along with the date, out of a database table that has values only for the present day.

      - For some reason, the date is stored as a numerical value in that table - I have myself made sure it is

      <=> My dilemma right now is that I don't quite remember what was the reason - there must have been a good one - that I stored the date in numeric form: That way, I cannot link that table to my master_calendar and the diagram does not work.

      Can anyone help me over the default of my memory, please?

      I can repair it by including a DATE() fct. in that LOAD statement - but I'm not sure of this because I don't remember why I chose to do it the other way in the first place.

       

      Thanks a lot!

      Best regards,

       

      DataNibbler

        • Re: Conflict of date format combined with the holiday-effect...
          Friedrich Hofmann

          Hi,

           

          it seems that I have been able to solve the problem, albeit at the price of another ;-)

          I have simply included one more RESIDENT LOAD before I store the resulting qvd file to get rid of the adapted date_field again.

          Since I cannot delete the other table, though, I get a synthetic key between those two.

          However, I would still like to know what was the compelling reason to store the date in this table in numeric format rather than date_format.

           

          Best regards,

           

          DataNibbler