D. Richard Hipp <d...@hwaci.com> wrote:
> On Feb 24, 2010, at 5:45 PM, Igor Tandetnik wrote:
>
>> D. Richard Hipp <d...@hwaci.com> wrote:
>>> This problem has existed in SQLite forever and has never been seen
>>> before. So it is obscure. The simple fix is to put the ON clause
>>> on the CROSS JOIN where it belongs.
>>
>> Does CROSS JOIN allow an ON clause? That doesn't make much sense. I
>> guess I'm missing something obvious.
>
> It does in SQLite. Maybe that isn't really sensible, but SQLite does
> it anyway. If it concerns you, simply rewrite as an INNER JOIN.
That would change the meaning of the OP's statement though. The goal is not to
limit the resultset to rows where c1.cur=c2.cur, but to annotate such rows in a
special way.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not necessarily a
good idea. It is hard to be sure where they are going to land, and it could be
dangerous sitting under them as they fly overhead. -- RFC 1925
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
