Re: possible bug in mysql 5.0.13

2005-10-13 Thread SGreen
Peter Brawley <[EMAIL PROTECTED]> wrote on 10/12/2005 04:27:18 PM: > James, > > Both ... > > SELECT ... > FROM a, b LEFT JOIN c ON a.x=c.y > > and > > SELECT ... > FROM a > LEFT JOIN B USING (x ) > LEFT JOIN c ON a.x=c.y > > work up to and including version 5.0.10, not in 5.

Re: possible bug in mysql 5.0.13

2005-10-12 Thread Peter Brawley
James, Both ...   SELECT ...   FROM a, b LEFT JOIN c ON a.x=c.y and   SELECT ...   FROM a     LEFT JOIN B USING (x )     LEFT JOIN c ON a.x=c.y work up to and including version 5.0.10, not in 5.0.11, 12 or 13. http://bugs.mysql.com/bug.php?id=13832 reports... "The two statements below

Re: possible bug in mysql 5.0.13

2005-10-12 Thread James Black
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > SELECT... > FROM items i > INNER JOIN nams.netids n > INNER JOIN ... > ... > Does the problem remain? If it goes away, this would be useful information > to include in your bug report. Thank you for the suggestion, but

Re: possible bug in mysql 5.0.13

2005-10-12 Thread SGreen
James Black <[EMAIL PROTECTED]> wrote on 10/12/2005 02:06:26 PM: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Peter Brawley wrote: > > James, > > > > You can reproduce that error by writing ... > > > > SELECT ... > > FROM a, b INNER JOIN c ON a.x=c.y > > > > The error goes away if

Re: possible bug in mysql 5.0.13

2005-10-12 Thread James Black
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Brawley wrote: > James, > > You can reproduce that error by writing ... > > SELECT ... > FROM a, b INNER JOIN c ON a.x=c.y > > The error goes away if you instead write ... > > SELECT ... > FROM b, a INNER JOIN c ON A.x=c.y > > so you

Re: possible bug in mysql 5.0.13

2005-10-12 Thread James Black
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Brawley wrote: > James, > > You can reproduce that error by writing ... > > SELECT ... > FROM a, b INNER JOIN c ON a.x=c.y > > The error goes away if you instead write ... > > SELECT ... > FROM b, a INNER JOIN c ON A.x=c.y I will t

Re: possible bug in mysql 5.0.13

2005-10-12 Thread Peter Brawley
James, You can reproduce that error by writing ...   SELECT ...   FROM a, b INNER JOIN c ON a.x=c.y The error goes away if you instead write ...   SELECT ...   FROM b, a INNER JOIN c ON A.x=c.y so you might try swapping FROM items i , nams.netids n PB - [EMAIL PROTECTED] wrote:

re: possible bug in mysql 5.0.13

2005-10-12 Thread SGreen
James Black <[EMAIL PROTECTED]> wrote on 10/12/2005 09:57:51 AM: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Due to the complexity of my query I don't know how to get this down to a > simple test case to demonstrate the error. > > This works under mysql 4.1.8 btw, so it is failing due

re: possible bug in mysql 5.0.13

2005-10-12 Thread James Black
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due to the complexity of my query I don't know how to get this down to a simple test case to demonstrate the error. This works under mysql 4.1.8 btw, so it is failing due to a change introduced recently. It also worked under mysql 5.0.9, but I haven'