----- Original Message ----- From: "Michael Stassen" <[EMAIL PROTECTED]> To: "Rhino" <[EMAIL PROTECTED]> Cc: "Marko Knezevic" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, August 31, 2004 4:17 PM Subject: Re: Multiple JOINs
> > Rhino wrote: > > > ----- Original Message ----- > > From: "Michael Stassen" <[EMAIL PROTECTED]> > > > >> > >>Rhino wrote: > >><snip> > >> > >>> The other thing that strikes me as a possible problem is the '&&' > >>> operator in the last join. I mostly use DB2 but it doesn't have this > >>> operator so I'm not completely sure what '&&' will do in a MySQL join. > >>> (I am familiar with the '&&' operator in programming languages, like > >>> Java, I've just never seen it used in joins before.) You might get a > >>> better result if you didn't use the '&&' operator and added another > >>> join for the Field_Lookup table. > >>> > >>>Rhino > >> > >>&& is a synonym for AND. See > >><http://dev.mysql.com/doc/mysql/en/Logical_Operators.html>. > >> > > > > Yeah, I saw that in the manual. Does it behave EXACTLY the same as the AND > > keyword? Or are there some subtle differences? > > > > Rhino > > The manual seems clear that they are synonyms. Did something lead you to > expect differences? > No, nothing specific. Just 20+ years of systems work that says sometimes, if the syntax is subtly different, the result is subtly different ;-) I'm probably just being paranoid though ;-) Rhino -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
