TechAuditBI commented on issue #26646: URL: https://github.com/apache/superset/issues/26646#issuecomment-2609376437
@mistercrunch Well, basically we just split a virtual dataset query into blocks by ";" and run everything that is not the last block before an actual viz query. After that we just use the last query block as superset would regularly. So expressions available to use in any part of the query are still regulated by checkboxes in DB parameters. F.e. if DML expressions are not allowed for DB user won't be able to use them in a "pre-query". All in all our main goal was mostly to allow users to create temp tables and use data returning procedures in their queries to lower overall data receiving times for dashboards. Also sometimes running a big nested query require db server to allocate huge amounts of memory to compute. Temp tables are used to overcome such a limitation. I think that we've managed to achieve our goal while avoiding adding some unnecessary UI elements. -- 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 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
