On May 10, Gozde Ozbal <gozba...@gmail.com> wrote: > I am using -d C:\IMDB-ftp -u mysql://root:123...@localhost/imdb
Seems fine. Are you using InnoDB or MyISAM tables? There are some options to improve performances, with InnoDB (but notice that MyISAM is _always_ faster, for our needs). > I am sorry that I cannot send you the output before the exception > in the error scenario, since I have been running the script for > approximately 10 hours and don't wanna halt it at the moment I fear that you'll end up with a lot of mess in your database anyway. :-/ Given the kind of errors, I think there's something serious, and it will prevent the data to be useful, sorry. > After this little change, I only receive lots of warnings like > C:\WorkSpace\tez\IMDbPY-4.1\imdbpy2sql.py:1107: Warning: Incorrect > string value: '\xC31536' for column 'phonetic_code' at row 1094 A real mess. :-) phonetic_code must be "AsciiChar+4digits", so I fear something is gone horribly wrong. > And please note that these warnings also exist for other columns > like note, name_pcode_nf and surname_pcode and I haven't changed > the lenghts of those. Do you have any idea about how these warnings > can be prevented? Sounds a bit like a configuration problem on your side, but I can't be too sure. Probably something about character-set/collation: in the README.sqldb file (in the docs) there are some example to fix it. My ideas for you: - stop the current elaboration. - leave the length of phoneticCode to 5. - put a single file (I'd start with movies.list.gz, trying with others if no problems occur) in an empty directory and use it as the "-d" argument of imdbpy2sql.py - try changing your MySQL configuration until you get no errors/warnings. In the next days, I'll try with MySQL 5.1 and the latest IMDb data. Thank you very much for your effort debugging the problem. -- Davide Alberani <davide.alber...@gmail.com> [GPG KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Imdbpy-help mailing list Imdbpy-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-help