rbock
6a9715b59d
Use clang-tidy to wrap single-line blocks into {}
2017-09-10 15:05:34 +02:00
rbock
c09a0b5ee8
Use clang-format to explicitly mark unused parameters
2017-09-10 14:58:51 +02:00
rbock
306ce63f2f
Use clang-format to add closing namespace comments
2017-09-10 14:56:51 +02:00
rbock
ac765993aa
Use clang-format to streamline include guards
2017-09-10 14:55:11 +02:00
rbock
5e52a4da46
Added a few auto alias tests
2016-12-25 21:25:01 +01:00
rbock
f029e5993b
Allow in() and not_in() to have zero arguments
...
This is then equivalent to in(value_list(some_empty_vector)) and
not_in(value_list(some_empty_vector):
tab.a.in() evaluates to false
tab.a.not_in() evaluates to true
2015-12-19 15:15:04 +01:00
rbock
173d6adbc9
Moved data types into separate folder, split boolean
...
Each file within data_types/boolean/ is relatively short and easy to
grok.
2015-10-29 22:21:46 +01:00
rbock
09f23cea0a
Reformatted using clang-format
...
Please use clang-format before submitting code, e.g via the pre-commit
supplied in the repo (thanks AndiDog)
2015-09-13 21:33:19 +02:00
Reto Schneider
5756b2355f
Remove trailing spaces.
2015-08-05 14:43:21 +02:00
rbock
2b8a36aa97
Added support for empty in() and not_in()
...
I wonder why SQL does not have that anyway.
2015-07-05 13:53:38 +02:00
rbock
864bd58eff
More functions are now auto-aliased
2015-07-05 11:51:49 +02:00
rbock
1e9910b12f
Replaced node tuple by node type vector
2015-02-17 08:03:19 +01:00
rbock
436ef67072
Replaced recursive traits with local traits which are evaluated recursively
...
Ok, that sounds weird...
Earlier, each node in the SQL tree had a struct containing all recursive
traits. This is now gone. It only contains a reference to all sub nodes
and its own specific traits.
2015-02-17 07:05:41 +01:00
rbock
97de6fad7f
Adjusted license dates
2015-02-15 19:00:21 +01:00
rbock
acba273230
Fixed a problem with sub selects in binary operators
...
There were missing braces for sub selects in expressions like
tab.id == select(max(tab.id)).from(tab).where(true)
2014-12-03 17:21:12 +01:00
rbock
74cafe35dd
We now have unique name representations per name
...
Before this, there could be multiple classes representing multiple id
columns. Now there is one class representing ALL the name "id". Very
important for analyzing potential name clashes.
2014-11-30 19:40:34 +01:00
