-
Notifications
You must be signed in to change notification settings - Fork 17k
teradatasql - 'LIMIT' keyword error #9600
Description
A clear and concise description of what the bug is.
Ji - I am using teradatasqlalchemy - teradatasql driver, connectiong to superset - connection is fine, I see my schemas & tables.
When I query a table - I get the below error on the keyword - 'LIMIT" - In other words - the SQL query which is generated by Superset, looks like has a default keyword 'LIMIT at the end - and Teradata doesn't accept keyword 'LIMIT'.
Expected results
Simple query should return rows from table
what you expected to happen.
Actual results
Get this error
base error: [Version 16.20.0.60] [Session 1583] [Teradata Database] [Error 3706] Syntax error: expected something between the word 'engines' and the 'LIMIT' keyword. at gosqldriver/teradatasql.(*teradataConnection).formatDatabaseError TeradataConnection.go:1138 at gosqldriver/teradatasql.(*teradataConnection).makeChainedDatabaseError TeradataConnection.go:1154 at gosqldriver/teradatasql.(*teradataConnection).processErrorParcel TeradataConnection.go:1217 at gosqldriver/teradatasql.(*TeradataRows).processResponseBundle TeradataRows.go:1712 at gosqldriver/teradatasql.(*TeradataRows).executeSQLRequest TeradataRows.go:548 at gosqldriver/teradatasql.newTeradataRows TeradataRows.go:416 at gosqldriver/teradatasql.(*teradataStatement).QueryContext TeradataStatement.go:122 at gosqldriver/teradatasql.(*teradataConnection).QueryContext TeradataConnection.go:2080 at database/sql.ctxDriverQuery ctxutil.go:48 at database/sql.(*DB).queryDC.func1 sql.go:1464 at database/sql.withLock sql.go:3032 at database/sql.(*DB).queryDC sql.go:1459 at database/sql.(*Conn).QueryContext sql.go:1701 at main.goCreateRows goside.go:652 at main._cgoexpwrap_212fad278f55_goCreateRows _cgo_gotypes.go:357 at runtime.call64 asm_amd64.s:574 at runtime.cgocallbackg1 cgocall.go:316 at runtime.cgocallbackg cgocall.go:194 at runtime.cgocallback_gofunc asm_amd64.s:826 at runtime.goexit asm_amd64.s:2361
what actually happens.
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Environment
Ubuntu 18.04 LTS
(please complete the following information):
- superset version:
superset version - python version:
python --version - node.js version:
node -v - npm version:
npm -v
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- I have checked the issue tracker for the same issue and I haven't found one similar.
Additional context
Add any other context about the problem here.
