diff options
| author | unknown <monty@mysql.com> | 2005-04-05 00:32:48 +0300 |
|---|---|---|
| committer | unknown <monty@mysql.com> | 2005-04-05 00:32:48 +0300 |
| commit | ae25f8df6ef53276d2051f193ed6e247da375e4d (patch) | |
| tree | 47a17106234067aa3cb031e4d92f9f332e28ce59 /BitKeeper | |
| parent | d17aebaa101c241968e6fe466f141f8682fb14e6 (diff) | |
| download | mariadb-git-ae25f8df6ef53276d2051f193ed6e247da375e4d.tar.gz | |
Now one gets an error if one tries to insert an invalid value via a stored procedure in STRICT mode. (Bug #5907)
client/mysqldump.c:
Changed some function and variable names to MySQL syntax
Fixed indentation for last few pushes
(No logic changes)
mysql-test/r/strict.result:
Test for bug #5907 (Traditional mode: invalid value can be inserted via a stored procedure)
mysql-test/t/strict.test:
Test for bug #5907 (Traditional mode: invalid value can be inserted via a stored procedure)
sql/sql_base.cc:
More comments
sql/sql_error.cc:
Ensure that PS gives error for invalid values in 'strict' mode
Diffstat (limited to 'BitKeeper')
0 files changed, 0 insertions, 0 deletions