On Dec 24, Davide Alberani <[EMAIL PROTECTED]> wrote: > That's really really bad, and right now I'm not able to reproduce > the problem.
Thanks to Fredrik Arnell, a couple of nasty bugs in imdbpy2sql.py script were fixed. I'm still unsure about what caused the segfault, but at least it should work correctly even in server configured with low values of max_allowed_packet, now. Anyway (MySQL users only), the suggest value of max_allowed_packet (to run imdbpy2sql.py script, at least ;-) is 8M or 16M. If you get many "TOO MANY DATA" warning, please change it. If this situation is very common, I suppose I should modify the imdbpy2sql.py script accordingly. -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Imdbpy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
