On Dec 01, Davide Alberani <[EMAIL PROTECTED]> wrote: > In the CVS there's something that a casual observer would define > something in between "experimental" and "totally demented". :-)
I've reverted most of changes. :-) It still works the same way, but: - a connection to the database is required and will be done. - constants will be read from the database. - tables containing only constants will not be created as CSV files. - indexes will be created, even if most of the tables will be empty. It still doesn't load the CSV files into the tables. Problems: - how to load the data? I assume we have to identify the right command for every database (neither SQLObject nor SQLAlchemy have a way to abstract this task, as far as I know). - some tables (think about cast_info) have an "id" column that is not created by the imdbpy2sql.py script and so it's not present in the CSV file. How to create it? I can save the name of the columns at the first row of a CSV file, but will be used by the database servers? - imdbIDs are lost, and it will be a major PITA, to restore them with CSV. -- 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
