You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently you can have comma-separated scans immediately following from, like this:
from e in emps, d in depts
but not following join. The following query is now legal:
from e in emps
where e.job = 'CLERK'
join d in depts,
l in locations
It's especially useful for declaring unbound variables:
from a, b
where a < b
join c, d, e, f
where a > 0
andalso b > 0
andalso c > 0
andalso d > 0
andalso e > 0
andalso f > 0
andalso a + b + c + d + e + f < 10
Also, you now can use on in from:
from e in emps, d in depts on e.deptno = d.deptno
Previously on was only allowed in join. on in the first scan after from was, and remains, illegal:
from e in emps on e.sal > 10, (*) illegal 'on'
d in depts
The text was updated successfully, but these errors were encountered:
…rom` clause
The following is now legal:
from a in [1, 2],
b in [3, 4, 5] on a + b = 6
where b < 5
join c in [6, 7] on b + c = 10,
d in [7, 8]
An `on` after the first scan, `from a in [1, 2]`, was and
remains illegal.
Remove Op.INNER_JOIN, because its semantics is identical to Op.SCAN.
(We will add operators back if and when we support `left join`.)
Fixeshydromatic#216
Currently you can have comma-separated scans immediately following
from
, like this:but not following
join
. The following query is now legal:It's especially useful for declaring unbound variables:
Also, you now can use
on
infrom
:Previously
on
was only allowed injoin
.on
in the first scan afterfrom
was, and remains, illegal:The text was updated successfully, but these errors were encountered: