On Fri, Dec 09, 2005 at 02:17:59PM -0500, Tom Lane wrote: > Michael Fuhr <[EMAIL PROTECTED]> writes: > > Hmm...I get errors in MySQL 5.0.16 with the query as posted so I > > have to wonder what the real query was. > > (tries it...) After removing the bogus comma, MySQL 4.1.14 swallows > the query without complaint, so it would seem that MySQL finally fixed > this bug at 5.0. I wonder what the OP's coworker will say when he tries > to migrate his code to 5.0 ...
Here we go: http://dev.mysql.com/doc/refman/5.0/en/join.html "Before MySQL 5.0.12, the comma operator (,) and JOIN both had the same precedence, so the join expression t1, t2 JOIN t3 was intrepreted as ((t1, t2) JOIN t3). Now JOIN has higher precedence, so the expression is interpreted as (t1, (t2 JOIN t3))." -- Michael Fuhr ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
