Timestamp MAKEDATE(2080,01,18) v MAKEDATE(2080,01,19)

[rustyfishbones]

Hi All,

I have stumbled across an issue with Tags for Timestamps

Why does Qlikview Tag 18/01/2080 as $numeric,$integer,$timestamp,$date.

But it Tags 19/01/2080 as $numeric,$integer

Why does it not read 19/01/2080 as a Timestamp or a Date

Regards

Alan

[MarcoWedel]

maybe the limit of the numerical representation of dates?

[rbecher]

The end is coming, eventually...

[MarcoWedel]

anything past 21st december 2012 is futile anyway

[rbecher]

Right, some early calendar bug..

However, 2080-01-19 still works as a date..

[MarcoWedel]

as the date calculations seem to work correctly with dates after 19/01/2080, maybe it's just a bug of the table viewer?

Maybe you could report it?

regards

Marco

[rustyfishbones]

Thanks Ralf,

I got a similar response from Stephen Redmond, I think it was

"Because that is when the world ends?"

Anyway it appears in Table Viewer, Also in Tables tab in Document Properties and when you hover over the field name after reload it shows tags as $numeric $integer but not $timestamp $date

Regards

Alan

[rustyfishbones]

Please see the below images

[stephencredmond]

QlikView has some functionality that, unless otherwise specified, will automatically interpret integers in a particular range as dates and will tag them accordingly.

I am not sure that it will break anything.  The fields are still stored as dates, they still take up 20 bytes each, they still work with Set Analysis expressions using the text dates.  All is good, except for the tag.  If that was going to be a concern, you can always manually tag it:

Tag Date1 with '$timestamp';

Tag Date1 with '$date';

Tag Date2 with '$timestamp';

Tag Date2 with '$date';

[rustyfishbones]

Thanks Stephen.

It's not a concern to be honest I was just wondering why it did not Tag dates after 19/01/2080 with $timestamp and $date

Regards

Alan