Kuba Podgórski
Kuba Podgórski
@gwellington - how `dep` tool is related to go modules? Moreover, this repo neither contain any `Gopkg` file nor vendor directory.
@aashishkapur - could you sign your PR? Thanks
I believe we should have more generic package like `go-mysql-index` which you can import like you import go's std. lib. `db` package and driver which will _anonymously_ implement the `Index`...
What if we do not have indexes on multiple columns (internally), so the index on (A, B) would be the same as index on A and index on B. Ultimately...
Ok, so I'll start prototype the idea of _dedup_ indexes (https://github.com/src-d/go-mysql-server/issues/261#issuecomment-430157020)
I noticed a small thing to improve. Having the following index: ``` CREATE INDEX email_idx ON commits USING pilosa (commit_author_email, commit_author_name); ``` Following `AND` query uses the index: ``` SELECT...
It's quite easy to fix the problem with index on (A, B) which can be used only with one condition, e.g.: ``` WHERE A = '...' ``` it may require...
@ajnavarro - right, it was just experiment, because with bitmaps it's doable. But actually with (A, B) only `A AND B` works. If you need `A OR B` you need...
Generally with bitmaps I don't see benefits of having multi-column indexes. It works better if we have index per expression and merge them because merging bitmaps is super fast and...
Notes from slack: --- If you create one index on expressions (A, B) , actually we don't index tuples, but independently A values and B values as pilosa fields, so...