[PossumX]

Originally Posted by GlowHost.com

That is an error generated by the MySQL server not the script itself. The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection.

You can read more about this problem and ask your host to increase the timeout if it is set too low. There can be other reasons as well. Here is a link that explains the error.

http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

As for the index, probably I will look at it a little closer later today and add it into the 2.0 version if its not there already.

My database is highly tuned, and there are no timeouts that occur on anything except this mod. I have a deep DBA background and have tuned as much as can be on MySQL dB. This is not a shot at you, by any means, however, I am quite sure my dB parameters are all in proper order, and considering the tables for this mod are very small, a simple insert or select should not induce the classic "MySQL has gone away errors". The question remains as to why this is only occurring against tables for this mod. None are crashed, however, I will re-analyze & check to ensure I am correct.

Thanks for your response, along with this mod, it is quite effective.

<<update>> I increased the wait timeout too see if that addresses the issue, and will refine from there if it does.