Add support for explicitly selecting from an index.#2057
Conversation
There was a problem hiding this comment.
comments for these? Especially whether they can both be true.
There was a problem hiding this comment.
+1. this should probably be an enum
There was a problem hiding this comment.
alternatively, maybe it's time to split this into separate types.
There was a problem hiding this comment.
Splitting into separate types is problematic due to the grammar changes. (I actually started out trying that approach and quickly gave up). Changing to an enum. It started as a single bool and then evolved.
|
Mostly LGTM. Some concern about the runtime assertions on |
|
@tamird The panics in |
5671414 to
bf2b96c
Compare
There was a problem hiding this comment.
can you add SELECT x FROM test.xyz@foo to exercise the error case? also nit from should be capitalized
There was a problem hiding this comment.
Done and done.
Yeah, that seems fine. My comment was intended to suggest that |
bf2b96c to
a5629be
Compare
|
LGTM |
There was a problem hiding this comment.
did you mean to add the select x case i described?
There was a problem hiding this comment.
Yes, though really I just misunderstood your comment and missed that error case. Good thing to add it because it found a bug.
Added support for "SELECT * FROM table@index". This is an extension which allows us to more explicitly test our index scanning. The index must exist within the table and the only columns accessible are those the index is defined on. See #2046.
ad50489 to
e0924c8
Compare
Add support for explicitly selecting from an index.
Added support for "SELECT * FROM table@index". This is an extension
which allows us to more explicitly test our index scanning. The index
must exist within the table and the only columns accessible are those
the index is defined on.
See #2046.