PL/SQL parser
(MDEV-10142)
|
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Parser, Prepared Statements |
| Affects Version/s: | None |
| Fix Version/s: | 10.2.3, 10.3.0 |
| Type: | Technical task | Priority: | Major |
| Reporter: | Alexander Barkov | Assignee: | Alexander Barkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Compatibility | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Sprint: | 10.2.2-3, 10.2.2-1, 10.2.2-2, 10.2.2-4, 10.1.18 | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
MariaDB allows to use only user variables in EXECUTE..USING:
Under terms of this task, we'll allow passing expressions as parameters to Dynamic SQL:
Note, these expression types should work as output parameters (in addition to user variables):
Note, stored functions and subselects as parameters will not be supported under terms of this task. Using stored functions and subselects would require some additional changes in table locking, SP cache and transaction handling (for the same reason, SET STATEMENT disallows stored functions and subselects as variable values). So the following scripts will return errors:
Support for stored functions and subselects as parameters (as well as in SET STATEMENT variable values) will be added under terms of a separate task. |