[adminer-tracker] [ adminer-Bugs and Features-3613109 ] Adding LIMIT 1 to DELETE/UPDATE statements

[SourceForge.net <no...@so...>]

Bugs and Features item #3613109, was opened at 2013-05-11 06:11
Message generated for change (Tracker Item Submitted) made by lome77
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1127745&aid=3613109&group_id=264133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: MySQL
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Lorenz (lome77)
Assigned to: Jakub Vrána (jakubvrana)
Summary: Adding LIMIT 1 to DELETE/UPDATE statements

Initial Comment:
Adminer always adds "LIMIT 1" to DELETE or UPDATE statements. We run a Master/Slave-SQL-Replication. The LIMIT 1 leads to this warning:

130509 22:30:57 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE `plots` SET `MINSTATUSREQUIRED` = '200' WHERE `ID` = '293' COLLATE utf8_bin AND `STATION` = '105' LIMIT 1

LIMIT 1 doesn't make sense in this kind of statements. Can it be removed?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1127745&aid=3613109&group_id=264133