Mybe, suggestion
| User, date | Message |
|---|---|
|
Written by BubikolRamios
2 years ago Category: General 273 posts since Thu, 14 Jan 10 |
I did check your source code and there is no "FOUND_ROWS()" string as far as I see. All together should speed things up (bringing total number of rows at data tab in HSQL) as said at MYSQL documentation. Did not look for, how you do it now. I did try to use it myself, here is what problems I came up with. http://www.codingforums.com/showthread.php?t=229346 Regards. |
|
Written by ansgar
2 years ago 3952 posts since Fri, 07 Apr 06 |
What should exactly get more speed? What's slow? I had a SELECT FOUND_ROWS() in Heidi in very old times where we did a SELECT SQL_CALC_FOUND_ROWS * FROM table LIMIT 0,1000 to get the number of rows in a limited result. But that SQL_CALC_FOUND_ROWS took to long as it works in a way similar to selecting rows with just no limit.I have the feeling I don't understand what you are exactly trying to ask or tell. |
|
Written by BubikolRamios
2 years ago 273 posts since Thu, 14 Jan 10 |
It is actualy not slow, but as I said, mysql doumentation says that SQL_CALC_FOUND_ROWS speeds thing up, and as you don't use it now I thought I could make a point. |
|
Written by ansgar
2 years ago 3952 posts since Fri, 07 Apr 06 |
You misinterpreted the documentation. SQL_CALC_FOUND_ROWS does not speed up anything. Sounds as if you don't know what it's for? |
|
Written by BubikolRamios
2 years ago 273 posts since Thu, 14 Jan 10 |
Quote: If you are using SELECT SQL_CALC_FOUND_ROWS, MySQL must calculate how many rows are in the full result set. However, this is faster than running the query again without LIMIT, because the result set need not be sent to the client http://dev.mysql.com/doc/refman/5.0/en/information-functions.html |
|
Written by kalvaro
2 years ago 441 posts since Thu, 29 Nov 07 |
Right, it's faster than running two queries. Does HeidiSQL run two queries? |
|
Written by BubikolRamios
2 years ago 273 posts since Thu, 14 Jan 10 |
Have no idea, did not look that deep (-: I imagined you run ' SELECT .... LIMIT ....' on each click on next button. |
|
Written by BubikolRamios
2 years ago 273 posts since Thu, 14 Jan 10 |
Ups, thought anse answered last post. |
|
Please login to leave a reply, or register at first. |