|
From: Anthony S. <sc...@gm...> - 2012-09-25 04:09:53
|
Hi Derek,
Can you please run the following command and report back what you see?
python -c "import tables; tables.test()"
Be Well
Anthony
On Mon, Sep 24, 2012 at 10:56 PM, Derek Shockey <der...@gm...>wrote:
> Hello,
>
> I'm hoping someone can help me. When I specify start and stop values
> for calls to where() and readWhere(), it is returning blatantly
> incorrect results:
>
> >>> table.readWhere("id == 'ceec536a-394e-4dd7-a182-eea557f3bb93'",
> start=3257, stop=table.nrows)[0]['id']
> '7f589d3e-a0e1-4882-b69b-0223a7de3801'
>
> >>> table.where("id == 'ceec536a-394e-4dd7-a182-eea557f3bb93'",
> start=3257, stop=table.nrows).next()['id']
> '7f589d3e-a0e1-4882-b69b-0223a7de3801'
>
> This happens with a sequential block of about 150 rows of data, and
> each time it seems to be 8 rows off (i.e. the row it returns is 8 rows
> ahead of the row it should be returning). If I remove the start and
> stop args, it behaves correctly. This seems to be a bug, unless I am
> misunderstanding something. I'm using Python 2.7.3, PyTables 2.4.0,
> and hdf5 1.8.9 on OS X 10.8.2.
>
> Any ideas?
>
> Thanks,
> Derek
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Pytables-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pytables-users
>
|