mirror of
https://github.com/MariaDB/server.git
synced 2026-04-24 01:05:30 +02:00
Cleanups
mysql-test/t/distinct.test: Cleanup sql/log.cc: Cleanup sql/slave.cc: Cleanup sql/sql_delete.cc: Cleanup sql/sql_parse.cc: Simple optimization
This commit is contained in:
parent
5e817c5313
commit
3c268e59ec
5 changed files with 48 additions and 39 deletions
|
|
@ -145,12 +145,15 @@ int mysql_delete(THD *thd, TABLE_LIST *table_list, COND *conds, ORDER *order,
|
|||
else
|
||||
{
|
||||
table->file->print_error(error,MYF(0));
|
||||
error=1; /* In < 4.0.14 we set the error number to 0 here, but that
|
||||
was not sensible, because then MySQL would not roll back the
|
||||
failed DELETE, and also wrote it to the binlog. For MyISAM
|
||||
tables a DELETE probably never should fail (?), but for
|
||||
InnoDB it can fail in a FOREIGN KEY error or an
|
||||
out-of-tablespace error. (Comment by Heikki July 7, 2003) */
|
||||
/*
|
||||
In < 4.0.14 we set the error number to 0 here, but that
|
||||
was not sensible, because then MySQL would not roll back the
|
||||
failed DELETE, and also wrote it to the binlog. For MyISAM
|
||||
tables a DELETE probably never should fail (?), but for
|
||||
InnoDB it can fail in a FOREIGN KEY error or an
|
||||
out-of-tablespace error.
|
||||
*/
|
||||
error= 1;
|
||||
break;
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue