diff options
author | unknown <andrey@lmy004.> | 2006-06-29 11:53:51 +0200 |
---|---|---|
committer | unknown <andrey@lmy004.> | 2006-06-29 11:53:51 +0200 |
commit | 8d961c45e2e83f04da92cbfc31d2975a6949743f (patch) | |
tree | a00b31b4c212c2306f408dd4bfd8a98df08b3d82 /regex/regcomp.ih | |
parent | 9fa9378b2e5713250e1262879c7bc4d999e1bb40 (diff) | |
download | mariadb-git-8d961c45e2e83f04da92cbfc31d2975a6949743f.tar.gz |
fix for bug#16394 "Events: Crash if schedule contains SELECT"
Parsing of CREATE/ALTER EVENT statement was crashing because of early
initialization done during parsing, instead in the after parsing phase.
Moreover, we don't want SUBqueries in CREATE/ALTER EVENT therefore we
disable them, though it is possible to make them work. It can be emulated
inside SP with a cursor and SP variable (CREATE/ALTER EVENT can still
accept variables as values).
mysql-test/r/events_bugs.result:
update result
mysql-test/t/events_bugs.test:
tests for bug#16384
sql/sql_yacc.yy:
disallow subqueries when SQLCOM_CREATE_EVENT | SQLCOM_ALTER_EVENT
The fix is not big, though lex->forbid_subqueries could have been introduced.
Easier is just to set the sql_command and check in both rules where
subqueries enter.
Diffstat (limited to 'regex/regcomp.ih')
0 files changed, 0 insertions, 0 deletions