Peter Brawley wrote:
/>Now this query is run over two tables and the ab_members table contains
>around 302 rows. Around 1/3 of these will be where cup=kids. However,
>when this query is run it returns 20,700 results /
That's because your ...
FROM ab_leader_board ablb, ab_members abm
calls for
>Now this query is run over two tables and the ab_members table
contains
>around 302 rows. Around 1/3 of these will be where cup=kids.
However,
>when this query is run it returns 20,700 results
That's because your ...
FROM ab_leader_board ablb, ab_members abm
calls for a cross join--it a
> Again, I implore all SQL coders to use the explicit JOIN syntax on all
> platforms that support it (Oracle being a well-known exception). It makes
Oracle supports the ANSI JOIN syntax from v9 and up.
> Shawn Green
As for the rest, I fully agree.
Martijn Tonies
Database Workbench - development
Schalk <[EMAIL PROTECTED]> wrote on 02/23/2006 08:55:01 AM:
> George Law wrote:
> > Schalk ,
> >
> > You need to specify the unifying column between your ablb and abm
tables.
> >
> > ie - in your where, "and ablb.id=abm.id"
> >
> > Once you get this so it returns expected results, you can run the
George Law wrote:
Schalk ,
You need to specify the unifying column between your ablb and abm tables.
ie - in your where, "and ablb.id=abm.id"
Once you get this so it returns expected results, you can run the
query, prefaced with
"explain" and it will give you an idea on the way mysql is runni
Schalk ,
You need to specify the unifying column between your ablb and abm tables.
ie - in your where, "and ablb.id=abm.id"
Once you get this so it returns expected results, you can run the query,
prefaced with
"explain" and it will give you an idea on the way mysql is running the
query. Thi
