I'll defer to you.
At 01:00 PM 5/28/2007, Baron Schwartz wrote:
>Dave Dyer wrote:
>>Thanks, it turns out you are exactly right. I rewrote
>>the query to keep the "on" immediately following the "left join"
>>and it now works as I wish.
>>I'll have to read up on "cross join", but if there
>>is a m
Dave Dyer wrote:
Thanks, it turns out you are exactly right. I rewrote
the query to keep the "on" immediately following the "left join"
and it now works as I wish.
I'll have to read up on "cross join", but if there
is a mysql bug here, it is that the parser that what I
wrote as "left join" was
Thanks, it turns out you are exactly right. I rewrote
the query to keep the "on" immediately following the "left join"
and it now works as I wish.
I'll have to read up on "cross join", but if there
is a mysql bug here, it is that the parser that what I
wrote as "left join" was turned into a cro
Dave Dyer wrote:
I'm trying to construct a join, but the effect I want seems
to be impossible to achieve. In this schema, the "uid"
field is unique in the "players" table, but not in the "ranking"
table (one player per uid, multiple rankings per player)
I want to select player names and rankin
I'm trying to construct a join, but the effect I want seems
to be impossible to achieve. In this schema, the "uid"
field is unique in the "players" table, but not in the "ranking"
table (one player per uid, multiple rankings per player)
I want to select player names and rankings for a particila
