I’m considering making a new language based on SQL SELECT statements to allow users to export CSV data in the manner they please. I’m confident in being able to interface this with a permissions system by inspecting the resulting AST from parsing before turning it into a SELECT statement to execute, so I’m not really concerned about this leading to unauthorized data access.
This language would be pretty much a 1-to-1 mapping of SQL SELECT statements, except for a few changes regarding joins and a few other things.
Users are relatively few and can be easily traced and contacted. It’s not the public at large.
The underlying DB would be MariaDB.
What should I be concerned about from this idea? If it’s a bad idea, why?
I thought about the possibility of making a query that doesn’t terminate by using
WITH RECURSIVE, so I’m not going to support that syntax, and I made the following question at the DBA SE to see what other ways a SELECT statement could be non-terminating (I thought of a few more while writing that question):
What are all the ways that a SELECT statement could be made to not terminate or take a very long time?
Besides that, is there anything more? Any particular risk? Is it possible to make some type of resource bomb with it, to consume all memory for example?
Access to this language could be put under a permission so only very privileged users could use it, but I wonder if that’s needed.