Hi Ben, Thanks for the reply. Actually that's the way my measurements come (a single number representing seconds since a reference epoch). What I need is to fractionate this number into the respective time elements (year, month, day, hour, secs, micro secs) and operate with them. So I would appreciate any suggestion on how to properly store (or represent) these on a very large table in order to be able to perform queries (without inconvenient transformations on the fly).
Thank you - Fernando On Wed, Nov 2, 2011 at 9:55 PM, Ben Elliston <b...@air.net.au> wrote: > Hi Fernando > > I don't know about datetime, per se, but you can also convert your > times/dates into time since Unix epoch and store that as a single > 64-bit integer. > > Cheers, Ben > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Pytables-users mailing list > Pytables-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pytables-users > -- Fernando Paolo Institute of Geophysics & Planetary Physics Scripps Institution of Oceanography University of California, San Diego 9500 Gilman Drive La Jolla, CA 92093-0225 web: fspaolo.net ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
