Steve, that’s just nutty. If those 513 rows are selected from a single table (not a big hairy join across bunches of tables) then they would have to be extraordinarily wide rows (tens of thousands of columns per row) before you would possibly be near any reasonable limit for request size. This doesn’t sound like it’s the real problem at all to me. Have you looked in your error logs — particularly in MySQL’s logs? What is the query, and what is the result when you ask for more than 512 rows?
Walter
On Nov 27, 2013, at 5:26 PM, SteveB wrote:
Hi all,
Just as a final update to this saga, I have found out the limit to how many rows the MySQL server will can handle before it fails; and that is 513, If you try to get 514 the server falls over with a 500 Internal Server Error.
This is something that shouldn’t happen as MySQL should be able to handle much more than this number of rows. I know that it should because it used to handle much more than this, which leads me to think that there is something wrong with the MySQL on the server.
I still haven’t been able to get a reply from James at Have Host as to whether there is a misconfiguration with the server.
The only way round this problem is to re configure the menus so that they don’t return more than 513 rows.
If I find a solution to this problem I’ll post an update, but until then I’ll struggle on with one hand tied behind my back.
Cheers,
Steve.
dynamo mailing list email@hidden Update your subscriptions at: http://freewaytalk.net/person/options
dynamo mailing list email@hidden Update your subscriptions at: http://freewaytalk.net/person/options