diff options
| author | unknown <guilhem@mysql.com> | 2005-10-17 10:52:34 +0200 |
|---|---|---|
| committer | unknown <guilhem@mysql.com> | 2005-10-17 10:52:34 +0200 |
| commit | 516699af2372f216b612c18c4c5657d31a909b2e (patch) | |
| tree | 9a116e2d4bda5c2a594cecd45221869ba5088984 /sql-common | |
| parent | ee74d3a54a933bdf4c33f4ea3e0fbed1701b4c69 (diff) | |
| download | mariadb-git-516699af2372f216b612c18c4c5657d31a909b2e.tar.gz | |
Fix for BUG#4544 "read_only also affects temporary tables":
the READ_ONLY global variable now allows statements which are to update only temporary tables
(note: if a statement, after parse stage, looks like it will update a non-temp table, it will be rejected,
even if at execution it would have turned out that 0 rows would be updated; for example
UPDATE my_non_tem_table SET a=1 WHERE 1 = 0; will be rejected).
sql/sql_parse.cc:
The READ_ONLY global variable now allows statements which are to update only temporary tables
(note: if a statement, after parse stage, looks like it will update a non-temp table, it will be rejected,
even if at execution it would have turned out that 0 rows would be updated; for example
UPDATE my_non_tem_table SET a=1 WHERE 1 = 0; will be rejected).
mysql-test/r/read_only.result:
result for new test
mysql-test/t/read_only.test:
test for READ_ONLY (there was none!) and for the new behaviour of READ_ONLY
Diffstat (limited to 'sql-common')
0 files changed, 0 insertions, 0 deletions