. :-)
It could also be an optimizer bug. What version of MySQL are you using?
Matt
- Original Message -
From: Keith Bussey
Sent: Monday, January 12, 2004 4:49 PM
Subject: JOIN types
Hey all,
I've read the pages in the MySQL manual that explain the types of
JOINs many
times
Keith Bussey wrote:
...
Also, I'm running MySQL 4.0.13-standard, STRAIGHT JOIN doesnt seem to exist
for me ;p
I think it is actually STRAIGHT_JOIN...
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Hey all,
I've read the pages in the MySQL manual that explain the types of JOINs many
times, but still think I'm missing something.
I usually was always using INNER JOIN in all my join queries, and in a few
cases LEFT JOIN (in cases I wanted the rows in one table that were not in the
other
I'm suprised by your result too. Did you have an index on the join column? If
not that might explain it. One place you might turn to learn more about how
mysql optimizes joins is internals.texi. This file describes a lot of the
internal workings of mysql and is found in the bk doctree and
bug. What version of MySQL are you using?
Matt
- Original Message -
From: Keith Bussey
Sent: Monday, January 12, 2004 4:49 PM
Subject: JOIN types
Hey all,
I've read the pages in the MySQL manual that explain the types of
JOINs many
times, but still think I'm missing something.
I
MyQuoting [EMAIL PROTECTED]:
I'm suprised by your result too. Did you have an index on the join column?
If
not that might explain it. One place you might turn to learn more about how
mysql optimizes joins is internals.texi. This file describes a lot of the
internal workings of mysql
I've been using LEFT JOIN and NATURAL LEFT JOIN for awhile on queries to
medium-sized tables (2500-50,000 items) that aren't TOO large by ane means,
but have seemingly been having some issues with this. Can anyone here
explain to me the memory usage between doing things like:
SELECT
