On Sat, Feb 16, 2013 at 3:01 AM, D L <dlm...@hotmail.com> wrote:
> The adding foreign keys bit has been taking roughly 8 hours. Should I
> restart the whole process or wait it out?

Seems really slow.
Is the db actually doing something?

Anyway, the creation of indexes/foreign keys and the store/restore
of imdbIDs at db updates seems to be slightly broken.
Any help fixing it is welcome.

> Once you have the database set up, is there a simple way to update it with
> the imdb text files they routinely release, or would you have to rerun the
> script with the new files?

Re-run the script with the new dataset.  No other way.
imdbIDs are (hopefully... se above) preserved between runs.

> If I'm making a webapp which could potentially receive a lot of requests,
> it'd be optimal to fetch the requests from the local database instead of
> through the web requests am I correct?

You're correct.

> Since the web requests scrapes the imdb pages and imdb frowns on that?

Main point, it's much slower.

Anyway, no matter what data you access (local or remote), I'm pretty sure
that the lIMDb license forbid you to use it for anything that is not
personal *and*
I.e.: no money (not even *saved* money) from it, and no public redistribution
of the data.


Davide Alberani <davide.alber...@gmail.com>  [PGP KeyID: 0x465BFD47]

The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
Imdbpy-help mailing list

Reply via email to