diff options
author | Carlo Zancanaro <carlo@clearboxsystems.com.au> | 2013-06-17 17:27:20 +1000 |
---|---|---|
committer | Carlo Zancanaro <carlo@clearboxsystems.com.au> | 2013-06-17 17:27:20 +1000 |
commit | b8fef59b7b85ae414ad64d2fb6540b3aea66602c (patch) | |
tree | d1f3a4a2d0e643a3c12d253a127489ec8e3e01d7 /README.md | |
parent | 4ab5ae273750c0d52ec72f103fe9165b52d2abb6 (diff) |
Rename sort-by, add grouping, refactor+fix some join stuff
`sort-by` is now called `sort`. This is just because I think it makes more
sense and nothing more.
Grouping has been added with `group` and `having`. They behave as you'd expect
from SQL, except that joining with a table which has a `group` or `having`
clause will move that query in as a subquery. I wasn't sure how else to ensure
their composition, so this way maintains the semantics (which is the most
important part) at the potential cost of some efficiency in performing the
query. I'm not sure that there exists a more general solution. I would assume
not.
The join stuff has been fixed a bit (some valid renames were rejected as
invalid) and standardised a bit (exceptions are now more similar). A bunch of
things have been added to the join stuff as a result of the above grouping
things, too. A bunch of changes all around, basically.
The compiler has also had a few small changes made to it, and has been enhanced
to support the grouping stuff.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions