On May 05, Davide Alberani <[EMAIL PROTECTED]> wrote: > 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.
I've updated the cvs with a version with support to indexes and tv series episodes. The user-side part is now fast, but the imdbpy2sql.py script is again as slow as hell (~6 hours to complete). The problem: we need 2 indexes on the CastInfo table, one for personID and one for movieID. Building these indexes at insert-time is incredibly slow (the db is already keeping track of a foreign key over the "role" column, plus the "id" primary key that we don't need but it's required by SQLObject). For some unintelligible reason SQObject won't permit to build indexes at a later time and the "id" column seems to be mandatory, even if it's not used. If there are no ideas my plan is: 1. release this slooow version as the 2.5. I don't want to delay too much a new release: there are very important news in other data access systems. 2. work on the 2.6 release, based on SQLAlchemy (or something else); this should at least spare us the "id" primary key. -- 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
