Showing all 20 (Edit, Save, CSV, Feed)
ID# Date Updated Type Status Sev Version Target OS Summary Assigned
711052013-12-06
16:00
2013-12-06
16:58
MySQL Server: ReplicationVerified
(1328 days)
S35.1.74, 5.5.35, 5.6.16AnyDELETE .. 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.8AnyUnexpected unsafety warning on automatic event drop Luis Soares
739362014-09-16
16:50
2014-09-16
16:50
MySQL Server: ReplicationOpenS35.6.20AnyIf 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
(161 days)
S35.7.13, 5.6.35,5.7.17AnyWarnings for statements flagged as unsafe  
586782010-12-02
22:36
2012-05-18
20:19
MySQL Server: ReplicationVerifiedS35.5.6, 5.5.8AnyWrong statement quoted in unsafety warning upon event execution Alfranio Correia
625372011-09-25
16:58
2012-01-09
13:20
MySQL Server: ReplicationVerified
(2035 days)
S35.5.20AnyFalse "unsafe statement" log report  
572502010-10-05
14:07
2017-05-21
20:45
MySQL Server: ReplicationVerified
(2486 days)
S25.1+Anymark 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-m3AnySBR mistakes SAVEPOINT statement for accessing a transactional table Alfranio Correia
552112010-07-13
13:50
2017-05-21
20:45
MySQL Server: ReplicationVerified
(2570 days)
S25.1+AnyINSERT...SELECT...LIMIT...UNION should be marked unsafe Assigned Account
636772011-12-08
17:50
2011-12-14
10:41
MySQL Server: ReplicationVerified
(2056 days)
S25.5.17, 5.5.19AnyStatement is incorrectly tagged as unsafe with triggers and auto increments  
817272016-06-05
8:10
2016-07-28
6:45
MySQL Server: ReplicationVerifiedS35.7.12AnyWarn It's Unsafe to Execute LOA DATA without Current DB  
710242013-11-27
11:35
2013-11-29
13:30
MySQL Server: ReplicationVerified
(1335 days)
S35.6.14Mac OS X (10.8)Safe statement marked as unsafe  
424152009-01-28
12:06
2017-05-21
20:45
MySQL Server: ReplicationVerified
(1658 days)
S35.1.30, 5.1.46AnyUPDATE/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
(224 days)
S35.6, 5.7.17, 8.0.0, 5.6.35AnyNot 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+Anymark reads from mysql.* and information_schema.* as unsafe Assigned Account
856392017-03-27
9:11
2017-07-24
12:49
MySQL Server: ReplicationVerifiedS35.7AnyXA transactions are 'unsafe' for RPL using SBR  
554812010-07-22
13:53
2012-05-18
20:19
MySQL Server: ReplicationVerified
(2561 days)
S25.1+5.1+AnyMark INSERT...SELECT into non-transactional table unsafe Assigned Account
434572009-03-06
14:24
2016-10-16
20:45
MySQL Server: ReplicationVerified
(3057 days)
S35.1, 6.0Anyreplicate-ignore-db behaves differently with different binlog formats Assigned Account
647582012-03-25
15:07
2012-03-27
7:31
MySQL Server: ReplicationVerified
(1949 days)
S35.5.20, 5.5.22AnyError 1592 is not selective enough  
529842010-04-20
13:02
2017-05-21
20:45
MySQL Server: ReplicationVerified
(2654 days)
S25.1+, mysql-trunkAnynon-binlogged unsafe statement causes switch to row if binlog_format=mixed Assigned Account
Showing all 20 (Edit, Save, CSV, Feed)