[MDEV-4679] PARSER - SANDBOX - parse queries without executing and report what happened Created: 2013-06-19 Updated: 2015-08-31 Resolved: 2014-01-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | roberto spadim | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Could be nice if we could parse queries without executing Example: 1st query) SET sandbox_on=1; RESULTS:
the create table could be used creating tables as TEMPORARY just to allow next queries to be executed without errors binary log is turned off in this case it's very nice to check if we have a sql injection or test a file of queries before executing them, since we can only do it with a running database and changing tables in a very big file is very difficult if we have a UPDATE or something that could be executed without seeking file query per query it's nice to build query tools like in JIRA when we don't need to create a parser, just allow user to write in WHERE part of query |
| Comments |
| Comment by Jean Weisbuch [ 2013-06-19 ] |
|
It looks like the PROFILE function mixed with some kind of transactionnal EXPLAIN. ps: EXPLAIN in 10.x is supposed to support CREATE/UPDATE/DELETE, maybe it could suffice to your needs. |
| Comment by roberto spadim [ 2013-06-19 ] |
|
that's the point of this 'sandbox' and not a profile Note: often the server does not need to execute SQL, only to parse it, so these classes should allow that too. since we will have it, why not expose to sql interface |
| Comment by roberto spadim [ 2013-06-19 ] |
|
maybe a UDF? |
| Comment by roberto spadim [ 2015-08-31 ] |
|
hi guys |