On Sun, Feb 12, 2012 at 21:17, Emmanuel Tabard <m...@webitup.fr> wrote: > >> Well, that's a very interesting solution, thanks. :-) > > I made a test run with this solution. > > Time to save/restore : 6minutes > > Restoring success : > > - People : 99.8777% > - Movies : 99.8845%
That's great! Ok, I've committed a compromise solution: when we're using CSV (which is thought to give you a set of files that you can move and restore on completely different db altogether), I use my previous implementation, but using a cursor instead of an ORM object (it should be really fast, at least storing the imdbIDs). When not using CSV, I've implemented your solution (the version based on a dbm database is also used as a fallback, in case some db servers have problems). But this is just the default: with the -i command line argument (by the way: I've removed -t to select a tmp directory: the CSV one is used or the current directory) you can force one method or the other: "-i dbm" and "-i table". I hope it works and it covers all the possible use cases. :-) -- Davide Alberani <davide.alber...@gmail.com> [PGP KeyID: 0x465BFD47] http://www.mimante.net/ ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
