Is there any possibility whatsoever that MySQL could go down or do some kind of weird time out under the pressure of a massive request? For example by clicking on the "all" button and it trying to return 100,000+ records?
Or would you know if it was for example possible for a memory setting to be set weirdly low, causing MySql to go away when a large request is entered?
I know the answers to both are pretty certain to be zero, but either this is some completely unique problem that is beating all the techs at 1&1, or they are being completely rubbish and not even looking for the problem at all, thinking it is this script causing the problem. Hence my serious need to narrow down the possibility completely to 1&1. 1&1 are now in to day 5 of supposedly looking at this issue you see and after 5 days of phoning and emailing them, i've had absolutely no joy out of them.