In the cvs there is the first beta of the new SQL data access system. The imdbpy2sql.py script has grown to be somewhat a mess, but it should work. I've tested it with mysql and postgres (not sqlite, yet - I'm not sure it will work).
With mysql, 2 hours were enough to process the whole database (~1.3 gigabyte of data, reversed in a ~1.6GB database). Unfortunately postgres is about 6 times slower, but it's all due to its implementation of the executemany method, so there's nothing we can do. On the user-side, it's still really slow: besides the ones defined by SQLObject, I've still not defined any Index; we need to work on that. It would be cool if we can tell SQLObject not to build indexes while inserting data, but to built it at the end of the process, but I'm not sure it's feasible. -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
