![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » Search Forums » Search Results » View Thread |
Messages 11 to 11 of 11 total |
![]() |
Wed, Sep 5 2012 9:22 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Raul, << I'm not sure but i think the MySQL optimizer likely resolves it back to proper inner join join if you just use where clause like you did >> Yes, more than likely. << it might be worthwhile to email elevate support and see if Tim can implement something like this in optimizer as well. >> Noooooooooo. ![]() reason for this is that the optimizer has to untangle the joins and make sure that there aren't any circular relationships (both EDB and DBISAM use nested-loop join architectures). Plus, the WHERE clause joins always being un-optimized is actually a nice advantage when you want to do "additional" WHERE clause processing on columns in two tables that are already being joined via a JOIN clause. It's the optimal way to execute such conditions. Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Saturday, June 22, 2024 at 05:51 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |