[Hornstar]

Originally Posted by Andrew Green

This is a fairly common one, you can solve it by going into phpmyadmin and adding a index to the "casino_settings" table on the "switch1" field.

Next release will involve a major remodeling of how a lot of the settings are stored and will eliminate it completely.

I am not sure if I am completely confident messing around in phpmyadmin unless it is a very last resort. I may just wait for the update or disable the casino until the update if the database errors keep flooding in too much more, however is this next update looking like it may come out this week end, or later (So I can gauge what my best solution is ).

Thanks.