On Nov 18, 2011, at 6:29 PM, Alan Marchiori wrote: > On Fri, Nov 18, 2011 at 9:21 AM, Josh Moore <josh.mo...@gmx.de> wrote: >> >> On Nov 17, 2011, at 10:35 PM, Alan Marchiori wrote: >> >>> I am attempting to use PyTables (v2.3.1) to store timestamped data and >>> things were going well until I added a column index. While the column >>> is indexed no data is returned from a table.where call! >>> >> >> I've reproduced with a number of different index configurations. If I change >> the column type to Float64, then the index works as expected. >> > ... > > Josh, > > Thanks for confirming this. It would seem indexing is broken on > Time64's (also the pytables unit tests do not catch this and unit > tests should probably be added for all indexable Col datatypes and/or > an error raised if you try to index on a non-indexable column). > Switching to Float64 works (floating point time since epoch) I just > have to ensure that gives sufficient precision for my data. Thanks, > problem solved and hopefully can be better handled in the next > release. > > Alan
Hi Alan, I filed an issue on github: https://github.com/PyTables/PyTables/issues/119 Thanks for pointing this out! ~Josh. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
