We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SELECT DISTINCT(1, 2);
ERRO[1415] mysql_server caught panic: unable to convert tuple type to SQL /home/mcuadros/workspace/go/src/github.com/src-d/gitbase/vendor/gopkg.in/src-d/go-mysql-server.v0/sql/type.go:690 (0x7cd7bb) com/src-d/gitbase/vendor/gopkg.in/src-d/go-mysql-server.v0/sql.tupleT.SQL: panic("unable to convert tuple type to SQL") /home/mcuadros/workspace/go/src/github.com/src-d/gitbase/vendor/gopkg.in/src-d/go-mysql-server.v0/server/handler.go:224 (0xc94c19) com/src-d/gitbase/vendor/gopkg.in/src-d/go-mysql-server.v0/server.rowToSQL: o[i] = s[i].Type.SQL(v) /home/mcuadros/workspace/go/src/github.com/src-d/gitbase/vendor/gopkg.in/src-d/go-mysql-server.v0/server/handler.go:137 (0xc941e8) com/src-d/gitbase/vendor/gopkg.in/src-d/go-mysql-server.v0/server.(*Handler).ComQuery: r.Rows = append(r.Rows, rowToSQL(schema, row)) /home/mcuadros/workspace/go/src/github.com/src-d/gitbase/vendor/gopkg.in/src-d/go-vitess.v1/mysql/conn.go:730 (0xb9f7f2) com/src-d/gitbase/vendor/gopkg.in/src-d/go-vitess.v1/mysql.(*Conn).handleNextCommand: err := handler.ComQuery(c, query, func(qr *sqltypes.Result) error { /home/mcuadros/workspace/go/src/github.com/src-d/gitbase/vendor/gopkg.in/src-d/go-vitess.v1/mysql/server.go:430 (0xbb0d5f) com/src-d/gitbase/vendor/gopkg.in/src-d/go-vitess.v1/mysql.(*Listener).handle: err := c.handleNextCommand(l.handler) /usr/lib/go/src/runtime/asm_amd64.s:1337 (0x45c1e0) goexit: BYTE $0x90 // NOP
Using truck at ca3ad0d
The text was updated successfully, but these errors were encountered:
Panic should not happen, but that's not a valid MySQL query.
Sorry, something went wrong.
Yes, should be SELECT DISTINCT 1, 2, as formulated is trying to do a DISTINCT on a tuple.
SELECT DISTINCT 1, 2
I know is not a valid query, but the server should never panic :D
juanjux
kuba--
Successfully merging a pull request may close this issue.
Using truck at ca3ad0d
The text was updated successfully, but these errors were encountered: