On May 10, Gozde Ozbal wrote:
> I have also made some changes about performance in MySQL
> configuration.
Good; another possible speed-up is to use imdbpy2sql.py to dump a set
of CSV files, later imported into the database. See README.sqldb
for the details.
By the way, the plain text data file
On May 11, Davide Alberani wrote:
> Maybe you can be interested in the Hollywood Informatics group,
You can find it here: http://groups.google.com/group/hollywood-informatics
--
Davide Alberani [GPG KeyID: 0x465BFD47]
http://erlug.linux.it/~da/
--
Davide,
You are right. After the check, I have realized that I was using InnoDB
tables. And at the end of 15 hours, the script was still running :) So I
have immediately stopped the current elaboration as you suggested. I've
changed the configuration to MyISAM tables also set
character-set-server
On May 10, Davide Alberani wrote:
> In the next days, I'll try with MySQL 5.1 and the latest IMDb data.
Everything is fine for me, after a fast test with a partial set of
data (5% of every plain text data file) and MySQL 5.1.34 with MyISAM
tables (standard configuration from Debian/sid).
I'm al
On May 10, Gozde Ozbal 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
Hi,
I am running imdbpy2sql.py on MySQL 5.1 and I am receiving an error like
below:
Traceback (most recent call last):
File "C:\WorkSpace\tez\IMDbPY-4.1\imdbpy2sql.py", line 2580, in
run()
File "C:\WorkSpace\tez\IMDbPY-4.1\imdbpy2sql.py", line 2424, in run
readMovieList()
File "C:\W
