diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2015-10-23 15:44:09 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2015-10-23 15:44:09 +0200 |
| commit | 22b59d8d176ea0d329dcd5b074f38640367ad02c (patch) | |
| tree | 070258600b27c7783c041014f44e3f6370d936a5 /feature/view/list | |
| parent | 8f6cda0dd7ce4504ebb661607213701004fddfc2 (diff) | |
Add feature: multiple (?) or order_by() in query condition
Diffstat (limited to 'feature/view/list')
| -rw-r--r-- | feature/view/list | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/feature/view/list b/feature/view/list index aa02062..2bd4bc8 100644 --- a/feature/view/list +++ b/feature/view/list @@ -1,3 +1,19 @@ +- Multiple (?) or order_by() in query condition + + Consider: + + #pragma ... query(foo.bar.not_null () && (?)) + + If we substitute "ORDER BY ..." for (?), then we will get "... AND ORDER BY" + in the statement. We can make it work by changing && to + but then if + we actually have additional conditions, that won't work. + + One idea: have order_by() pragma? Though we can also have LIMIT, OFFSET, + etc. This should also align with ORDER BY, etc syntax in general queries. + + Another idea: support multiple (?) that are "filled" from multiple + query() arguments (C++11 variadic template). + - Member names for table views Currently we have to specify column names as strings in table views queries. |