maxgillmaxgill opened a new issue, #26876:
URL: https://github.com/apache/superset/issues/26876
### Bug description
I get a "FATAL ERROR" when I try to save a dataset from SQL Lab that looks
like this:
`SELECT
COL_ID as ID,
COL_DESCRIPTION as DESCRIPTION,
COL_CREATEDDATE as CREATEDDATE,
COL_TAG as TAG,
COL_VIEWCOUNT as VIEWCOUNT
FROM {{ecx_schema}}.tbl_kbtag`
But I don't get an error if I save it like this:
`SELECT
COL_ID as ID,
COL_DESCRIPTION as DESCRIPTION,
COL_CREATEDDATE as CREATEDDATE,
COL_TAG as TAG,
COL_VIEWCOUNT as VIEWCOUNT
FROM my_schema.tbl_kbtag`
While it would be good to be able to save these datasets and pre-populate
the jinja params in the new dataset, simply explaining the error instead of
"Fatal Error" would be a good start.
### How to reproduce the bug
1. Go to SQL Lab
2. Create an SQL query with the schema name in a Jinja template
3. Click Save Dataset
### Screenshots/recordings
### Superset version
3.0.3
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [X] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
