Andrés Taylor

@derekperkins I'm sorry if I left you with the impression that query planning is just string parsing. What I meant was more that PGO could probably help a lot of...

Hi @wangweicugw! Thanks for looking into this. Your solution would not work for a slightly more complex query - basically any column inside a UNION or derived table that is...

Update with a bit about conflicts with USE & IGNORE VINDEX

> I am unsure why we cannot add support `FOR {JOIN|ORDER BY|GROUP BY}`. For the `Join` still, there are 2 routes and the table indicates the hint and uses the...

> how about issuing a warning over failing the query for vindexes that do not exists? We can fail when the user uses both `USE` and `IGNORE` on the same...

@ejortegau wdyt - can you fix the conflicts so we can get it merged?

Yeah, you would need to add the constant to `go/mysql/constants.go`, something like: ``` ComStatistics = 0x08 ```

Hmm... good point. I misunderstood your question. If I were you, I would reproduce @aquarapid 's experiment and use wireshark or something like it to see what is going on....

FYI - I used the `explain select...;show warnings;` trick to see what mysql rewrites queries to.

Here is a list of the queries used to show the above table: ```sql # WHERE when the table column matches select val1 as foo from aggr_test where val1 =...