It worked fine (106 minutes with 2 dual core opterons and 4GB of ram). Only
thing I noticed is a lot of these messages popping up while it was running.
I'm not sure they were happening before.
SCANNING actor: Hammer, M.C.
SCANNING actor: Hannon, Chick
* FLUSHING PersonsCache...
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
4398
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
1498
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
1282
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
2550
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
12970
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
5855
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
13669
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'note' at row 15666
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
6557
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'person_role' at row
17060
CURS.executemany(self.sqlString, self.converter(self.values()))
imdbpy2sql.py:727: Warning: Data truncated for column 'note' at row 12462
CURS.executemany(self.sqlString, self.converter(self.values()))
* FLUSHING SQLData...
SCANNING actor: Hardwick, Paul
SCANNING actor: Harper, Robert (I)
* FLUSHING SQLData...
SCANNING actor: Harrison, Todd
SCANNING actor: Harvey, Robert (I)
* FLUSHING SQLData...
I seemed to remember it being related to the max_packet_size variable, so I
set it to 32M and it still happened. Does it need to be higher or is it
unrelated?
Thanks very much for your help.
On 5/10/07, Davide Alberani <[EMAIL PROTECTED]> wrote:
On May 10, Sabo <[EMAIL PROTECTED]> wrote:
> Thanks. The original CVS version gave this:
[...]
> TypeError: build_title() got an unexpected keyword argument
'_emptyString'
Wait: it seems that you're using the imdbpy2sql.py script from the
CVS, but you've not installed the imdbpy package from the CVS.
I've modified also the packages, and not only the script: run
python ./setup.py install
If the problem is not fixed, let me know!
HTH,
--
Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47]
http://erlug.linux.it/~da/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Imdbpy-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Imdbpy-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
