Hello,
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!
This behavior is demonstrated with the following test code:
---begin test.py---
import table
On Fri, Nov 18, 2011 at 9:21 AM, Josh Moore 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
I am trying to allow multiple threads read/write access to pytables data
and found it is necessary to call flush() before any read. If not, the
latest data is not returned. However, this can cause a RuntimeError. I
have tried protecting pytables access with both locks and queues as done by
josha
Tables will release the GIL when making
> HDF5 library calls, so the other threads will be able to run. You could
> use a Queue.Queue or some other mechanism to transfer data between
> threads. No actual copying would be needed since their memory is shared,
> which should make it
start = datetime.datetime.now()
# run for 10 seconds
while (datetime.datetime.now() - start <
datetime.timedelta(seconds=10)):
# randomly do a read or a write
if random.random() > 0.5:
t.write()
else:
t.read()
print t.stats
seems to be gone in all versions of my test program (both
single threaded and threaded with locks). Hope this helps someone else and
eventually maybe someone will figure out what is wrong with File.flush().
On Mon, Dec 10, 2012 at 10:52 AM, Alan Marchiori wrote:
> I'm continuing to fi
