List:General Discussion« Previous MessageNext Message »
From:SGreen Date:October 12 2005 7:27pm
Subject:Re: possible bug in mysql 5.0.13
View as plain text  
James Black <jblack@stripped> 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 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 
> 
>   Tried that,now I get:
> Unknown column 'n.badge'in 'on clause'
> 
>   So, whichever order I put them in, I get one of two errors.
> 
>   It appears that this bug will continue to break for me until it is
> fixed in the next version, hopefully.
> 
> - --
> "Love is mutual self-giving that ends in self-recovery." Fulton Sheen
> James Black    james@stripped
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFDTVCiikQgpVn8xrARAqGjAJ9y4/ym15QPZj8KVvbyuIkmTIKMKACfTlP9
> cd7w92nB8uhOH2Y1+jAe4MU=
> =FOcN
> -----END PGP SIGNATURE-----


What if, instead of using a comma, you use an explicit INNER JOIN? It's 
perfectly valid to leave out the ON clause of an INNER JOIN (creating a 
Cartesian product).  I mention this because you don't seem to have a term 
to use in an ON clause, unless you want to move the term n.netid='jblack' 
from the WHERE clause. 

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.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
Thread
re: possible bug in mysql 5.0.13James Black12 Oct
  • re: possible bug in mysql 5.0.13SGreen12 Oct
    • Re: possible bug in mysql 5.0.13Peter Brawley12 Oct
      • Re: possible bug in mysql 5.0.13James Black12 Oct
      • Re: possible bug in mysql 5.0.13James Black12 Oct
        • Re: possible bug in mysql 5.0.13SGreen12 Oct
          • Re: possible bug in mysql 5.0.13James Black12 Oct
          • Re: possible bug in mysql 5.0.13Peter Brawley12 Oct
            • Re: possible bug in mysql 5.0.13SGreen13 Oct