John Gill (el 2007-07-24 a les 17:25:25 +0100) va dir:: > [...] > For instance, createIndex() fails, as does ptrepack (this is with python > 2.5 on a 32 bit machine). > > How hard is it to fix the pytables code for these bits to work around > the limits? > [...]
Hi John,
I think the best way for us to unearth those problems will be to try and
index a table with, say 2**31 rows. Hopefully the problems will also
arise from using table lengths instead of ``nrows``, but I can't tell
for sure without running some tests and having a look at some code.
It seems that those errors silently slipped in because we do happen to
use Python 2.5 on a 64-bit machine to test PyTables against such great
amounts of data! Fortunately, we can still run the same tests under 2.4
to force the failures to show.
I think this won't be exceedingly hard to fix, but tests may be a little
slow with so much data. I'm having a look at it... ::
> It looks that for now, I'll have to keep tables below 1 billion records
> if I don't want to move to a 64 bit machine.
I think you can raise that figure to 2**31 - 1 without problems, if that
may come handy.
Regards,
::
Ivan Vilata i Balaguer >qo< http://www.carabos.com/
Cárabos Coop. V. V V Enjoy Data
""
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
