It's easy enough to swap timespan for timestamp in tick.q, but I wascurious why timespan is the default.For rdb queries and other tick.q subscribers, I find that I often wantto compare the relative values of two timespans, but can't because thedate isn't recorded until saving down to the hdb.Isn't using the timestamp type the obvious solution here? I get thatthe date component of timestamp would be redundant in the hdb, but whatother solution is there for real-time data?Thanks,Josh
X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHM71PTfjR2Gt5nyXbQdRtzgokoEgJPflBmAbQOmxmfCxRPAA== Content-Language: de
The tp is also responsible to send the eod signal. So with .z.P it will = also be able to check whether the day has switched or not.
-----Urspr=C3=BCngliche Nachricht----- Von: firstname.lastname@example.org = [mailto:email@example.com] Im Auftrag von = firstname.lastname@example.org Gesendet: Montag, 8. Februar 2016 15:33 An: email@example.com Betreff: Re: [personal kdb+] Re: use of timespan in tick.q
I am using the standard tick.q.
While it does call .z.P, it only retains the timespan portion:
Like I said, it's trivial to alter, but was just curious why timespan is = the default.