Josh Trutwin [EMAIL PROTECTED] wrote on 09/20/2004 10:41:46 PM:
On Mon, 20 Sep 2004 10:25:16 -0400
[EMAIL PROTECTED] wrote:
I think you missed my point. I think the 5.0.1 behavior was correct
and the others are wrong. There is a known bug (or two) about mixing
outer joins and inner
On Tue, 21 Sep 2004 08:57:21 -0400
[EMAIL PROTECTED] wrote:
snip
There are up to three layers of record filtering that happen during
any query. First is the JOIN filtering. That is where the ON
conditions are used with the table declarations to build a virtual
table that consists of all
Josh Trutwin [EMAIL PROTECTED] wrote on 09/21/2004 09:40:03 AM:
On Tue, 21 Sep 2004 08:57:21 -0400
[EMAIL PROTECTED] wrote:
snip
snip again
Perhaps another example would help. I've been trying to re-write
another join query that's designed to produce an attendance record for
each
On Tue, 21 Sep 2004 10:49:31 -0400
[EMAIL PROTECTED] wrote:
Hmmm. you want to see a student, all of the classes they are
enrolled in and how many times they attended? I understand the
relationships between the student, class, and class_attended tables
(that's all related to attendance and
Thanks! Between the ERD and your descriptions I think I've got it. Most of
the others on this list who have designed a system like yours (gradebooks
or attendance taking) designed it so that it supported multiple
instructors for multiple courses each of which have their own class
schedules (at
Sounds like your 4.0.20 may be the buggy installation... let me see if I
can explain.
Let's analyze your FROM clause and imagine there is no WHERE clause, for
the moment:
FROM student s
INNER JOIN enrollment e ON e.tech_id = s.tech_id
INNER JOIN submitted_assignment sa ON sa.tech_id =
On Mon, 20 Sep 2004 09:33:56 -0400
[EMAIL PROTECTED] wrote:
Sounds like your 4.0.20 may be the buggy installation... let me see
if I can explain.
Except this is a 5.0.1 installation. The query worked as is in 4.0.20
(and it also worked in 5.0.0), only after playing with 5.0.1 did the
results
I think you missed my point. I think the 5.0.1 behavior was correct and
the others are wrong. There is a known bug (or two) about mixing outer
joins and inner joins and it looks like it may be fixed. IF you want to
see all of the students THAT TABLE (students) needs to be on the LEFT side
of a
On Mon, 20 Sep 2004 10:25:16 -0400
[EMAIL PROTECTED] wrote:
I think you missed my point. I think the 5.0.1 behavior was correct
and the others are wrong. There is a known bug (or two) about mixing
outer joins and inner joins and it looks like it may be fixed. IF
you want to see all of the
Is there a known bug with outer joins in MySQL 5.0.1?
I tried the following query on 5.0.1:
SELECT s.tech_id, s.full_name, sa.points_awarded, sa.date_submitted
FROM student s
INNER JOIN enrollment e ON e.tech_id = s.tech_id
INNER JOIN submitted_assignment sa ON sa.tech_id = s.tech_id
RIGHT JOIN
10 matches
Mail list logo
