John- > or would it be a 32-bit integer or 64-bit integer?
We¹d use a time_t (or put the value into a time_t) so that it can be used by the time functions. I think time_t is 32 or 64 bits depending on the platform. Essentially we¹d take the time_t and pass it to localtime_r which would return a Œstruct tm¹ in the proper timezone at query time. We wouldn¹t store the Œstruct tm¹ since it would differ depending on what the timezone is at query time. Sean On 3/3/14, 11:55 AM, "K. John Wu" <[email protected]> wrote: >Hi, Sean, > >What you are saying seems reasonable to me. Presumably, the real data >will be in 'struct tm', right? or would it be a 32-bit integer or >64-bit integer? > >John > > >On 2/28/14, 2:27 PM, Sean McNamara wrote: >> Hi- >> >> I am working with timeseries data and find myself wanting fastbit to >> group by a time format that I would pass into strftime. The goal >> would be to have the epoch time in a column and at query time choose a >> timezone and format. It seems like it would be possible doing >> something like the ibis::math::term and the stdfun2 functions. >> >> Would one need to subclass ibis::qExpr and create a qDate class or >> something to accomplish this? Thoughts? >> >> Thanks, >> >> Sean >> >> >> _______________________________________________ >> FastBit-users mailing list >> [email protected] >> https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users >> >_______________________________________________ >FastBit-users mailing list >[email protected] >https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users _______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
