Showing all 20 (Edit, Save, CSV, Feed)
ID# Date Updated Type Status Sev Version Target OS CPU Summary Assigned
711052013-12-06
16:00
2013-12-06
16:58
MySQL Server: ReplicationVerified
(1753 days)
S35.1.74, 5.5.35, 5.6.16AnyAnyDELETE .. ORDER BY .. LIMIT is safe in some cases  
586842010-12-02
23:45
2012-05-18
20:19
MySQL Server: ReplicationVerifiedS35.5.6, 5.5.8AnyAnyUnexpected unsafety warning on automatic event drop Luis Soares
739362014-09-16
16:50
2018-07-31
9:38
MySQL Server: ReplicationVerified
(55 days)
S35.6.20AnyAnyIf the storage engine supports RBR, unsafe SQL statementes end up in binlog  
849712017-02-13
21:11
2017-02-15
7:17
MySQL Server: ReplicationVerified
(586 days)
S35.7.13, 5.6.35,5.7.17AnyAnyWarnings for statements flagged as unsafe  
586782010-12-02
22:36
2012-05-18
20:19
MySQL Server: ReplicationVerifiedS35.5.6, 5.5.8AnyAnyWrong statement quoted in unsafety warning upon event execution Alfranio Correia
625372011-09-25
16:58
2012-01-09
13:20
MySQL Server: ReplicationVerified
(2460 days)
S35.5.20AnyAnyFalse "unsafe statement" log report  
572502010-10-05
14:07
2017-05-21
20:45
MySQL Server: ReplicationVerified
(2911 days)
S25.1+AnyAnymark INSERT...SELECT with autoinc column unsafe when innodb_autoinc_lock_mode=2 Assigned Account
545622010-06-16
19:18
2017-05-21
20:45
MySQL Server: ReplicationVerifiedS35.5.3-m3, 5.5.5-m3AnyAnySBR mistakes SAVEPOINT statement for accessing a transactional table Alfranio Correia
552112010-07-13
13:50
2017-05-21
20:45
MySQL Server: ReplicationVerified
(2995 days)
S25.1+AnyAnyINSERT...SELECT...LIMIT...UNION should be marked unsafe Assigned Account
636772011-12-08
17:50
2011-12-14
10:41
MySQL Server: ReplicationVerified
(2481 days)
S25.5.17, 5.5.19AnyAnyStatement is incorrectly tagged as unsafe with triggers and auto increments  
817272016-06-05
8:10
2016-07-28
6:45
MySQL Server: ReplicationVerifiedS35.7.12AnyAnyWarn It's Unsafe to Execute LOA DATA without Current DB  
710242013-11-27
11:35
2013-11-29
13:30
MySQL Server: ReplicationVerified
(1760 days)
S35.6.14Mac OS X (10.8)AnySafe statement marked as unsafe  
894672018-01-30
9:34
2018-06-13
12:37
MySQL Server: ReplicationVerified
(234 days)
S38.0.4AnyAnyRedundant GTID unsafe mark for CREATE/DROP TEMPORARY TABLE in RBR/MBR  
424152009-01-28
12:06
2017-05-21
20:45
MySQL Server: ReplicationVerified
(2083 days)
S35.1.30, 5.1.46AnyAnyUPDATE/DELETE with LIMIT clause unsafe for SBL even with ORDER BY PK clause Assigned Account
841852016-12-13
14:07
2016-12-14
7:20
MySQL Server: ReplicationVerified
(649 days)
S35.6, 5.7.17, 8.0.0, 5.6.35AnyAnyNot all "Statements writing to a table with an auto-increment..." are unsafe  
483822009-10-28
16:12
2016-10-16
20:45
MySQL Server: ReplicationVerifiedS25.1+AnyAnymark reads from mysql.* and information_schema.* as unsafe Assigned Account
887202017-11-30
14:52
2018-02-24
10:49
MySQL Server: ReplicationVerified
(297 days)
S35.6, 5.7, 8.0.3, 5.6.38, 5.7.20AnyAnyInconsistent and unsafe FLUSH behavior in terms of replication  
554812010-07-22
13:53
2012-05-18
20:19
MySQL Server: ReplicationVerified
(2986 days)
S25.1+5.1+AnyAnyMark INSERT...SELECT into non-transactional table unsafe Assigned Account
647582012-03-25
15:07
2012-03-27
7:31
MySQL Server: ReplicationVerified
(2374 days)
S35.5.20, 5.5.22AnyAnyError 1592 is not selective enough  
529842010-04-20
13:02
2017-05-21
20:45
MySQL Server: ReplicationVerified
(3079 days)
S25.1+, mysql-trunkAnyAnynon-binlogged unsafe statement causes switch to row if binlog_format=mixed Assigned Account
Showing all 20 (Edit, Save, CSV, Feed)