As suggested by Joachim, to improve performace of the poor old imdbpy2sql.py script we could explore the possibility to write the data in a CSV format, to be later loaded on the database (at least for the first version, I'd be satisfied to have the CSV files writter, leaving to the user to load it).
Now... we have a total of 6 calls to the executemany method of a cursor object - these calls actually insert _all_ the data in the database. The are also 6 other calls to the 'execute' method, 4 are not really used in the code (they are used if you manually populate some of the *Cache classes, mostly for debugging purposes) and two executes custom queries. Overriding (or encapsulating) the executemany of a cursor object (probably of a "fake" cursor object) will be easy enough to write the information to a set of files, instead of a database. Now, the question is: is there a (more-or-less) universal format of CSV file accepted by all/most-of the database servers out there? :-) -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
