| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Perrin Harkins | Date: | February 3 2009 6:46pm |
| Subject: | Re: WHERE vs. ON | ||
| View as plain text | |||
On Tue, Feb 3, 2009 at 12:24 PM, Jerry Schwartz <jschwartz@stripped> wrote: > Somebody, I think it was somebody from MySQL, said that you should never put > anything into a WHERE clause that could be put into the ON clause of a JOIN. > My guess is that this helps with the optimization, but it seems > counter-intuitive to me. It seems like it shouldn't make any difference if the optimizer is smart enough, but in my experience it sometimes does. Because of that, I always try to put conditions in the ON clauses when I can, even if they are not about joining the tables. - Perrin
| Thread | ||
|---|---|---|
| • WHERE vs. ON | Jerry Schwartz | 3 Feb |
| • RE: WHERE vs. ON | Martin Gainty | 3 Feb |
| • RE: WHERE vs. ON | Jerry Schwartz | 3 Feb |
| • Re: WHERE vs. ON | Rob Wultsch | 3 Feb |
| • Re: WHERE vs. ON | Perrin Harkins | 3 Feb |
| • Re: WHERE vs. ON | Baron Schwartz | 4 Feb |
| • RE: WHERE vs. ON | Jerry Schwartz | 4 Feb |
| • Re: WHERE vs. ON | John Daisley | 4 Feb |
| • RE: WHERE vs. ON | Jerry Schwartz | 4 Feb |
| • Re: WHERE vs. ON | Claudio Nanni | 4 Feb |
| • Re: WHERE vs. ON | Martijn Tonies | 4 Feb |
