2 ms·
MySQL always did more than nested loop joins -- which is literally the worst kind of join. It's the join you get if you have no indexes on anything in any DBMS
by wvenable 12y ago
MySQL always did more than nested loop joins -- which is literally the worst kind of join. It's the join you get if you have no indexes on anything in any DBMS. I fail to see what your reply here is trying to refute.
Even your comment, stating that MySQL doesn't maintain statistics, it's totally wrong and easily checked with 5 seconds of Googling.
To your edit: The idea that a DBMS would support so many advanced features and do nested loop joins is laughably ridiculous.
- dsp1234 12y agoI'm no MySQL expert, but the docs for 5.6 specifically state: "MySQL resolves all joins using a nested-loop join method." [0] Can you provide documentation on other join methods? [0] - http://dev.mysql.com/doc/refman/5.6/en/explain-output.html http://dev.mysql.com/doc/refman/5.6/en/explain-output.html
- wvenable 12y agoMySQL sort-merge joins, it's right in that documentation, but it calls everything out as optimizations on nested-loop. http://www.xaprb.com/blog/2013/10/01/mysql-isnt-limited-to-nested-loop-joins/ http://www.xaprb.com/blog/2013/10/01/mysql-isnt-limited-to-n... It doesn't do hash joins which is the biggest limitation but MySQL is pretty good a joins and certainly was never bad enough to warrant it's reputation. It's toolbox is smaller than other RDBMS products but it's not empty.
- saosebastiao 12y agoYou claim that MySQL always did more than nested loop joins, and yet the features cited in that blog post were introduced in version 5.6, which was released in 2013... Several years after the other advanced features that supposedly preclude MySQL from doing something as stupid as nested loop joins.
- deleted 12y ago[deleted]
- saosebastiao 12y ago> The idea that a DBMS would support so many advanced features and do nested loop joins is laughably ridiculous. Correct. MySQL is laughably ridiculous.