I figured it out. My default table type was innodb. I changed this in my.cnf to myisam and it fixed the problem. Thanks for all your help!
-----Original Message----- From: Davide Alberani [mailto:[EMAIL PROTECTED] Sent: Friday, May 02, 2008 12:25 PM To: [email protected] Cc: Matt Warnock Subject: Re: [Imdbpy-devel] FW: ZeroDivisionError: integer division or modulo by zero On May 02, Matt Warnock <[EMAIL PROTECTED]> wrote: > Unfortunately raising my max_allowed_packet to 8M, 16M and 32M > didn't fix anything. :-/ As a last note, my system is configured this way: key_buffer = 16M max_allowed_packet = 16M thread_stack = 128K query_cache_limit = 1048576 query_cache_size = 16777216 query_cache_type = 1 > I restarted mysql and verified the setting stuck: Always managing the 'plot' list, right? Did you get other "splitting" warnings on other lists? As said, the last resort is to set MAX_RECURSION to a lower value, but some (many?) data will be missing. I really can't think of any other possible cause of this behavior, and I don't have other reports about it. Thanks for your tests! -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Imdbpy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
