Showing all 10 (Edit, Save, CSV, Feed)
ID# Date Updated Type Status Sev Version OS CPU Summary
86532005-02-21
16:33
2005-04-06
15:09
MySQL ServerClosed
(6931 days)
S1 Any5.0.3 leaves an InnoDB trx open after connection ends; InnoDB shutdown hangs
118252005-07-08
21:10
2005-08-05
21:43
MySQL Server: DocumentationClosed
(6810 days)
S45.0.8-beta-nightly-20050618N/AAnyClarify whether innodb_flush_log_at_trx_commit preserves crash-recovery
120982005-07-21
22:08
2005-08-21
22:21
MySQL Server: DocumentationClosed
(6794 days)
S3Your Web SiteYour Web SiteAnyMySQL Reference Manual: "lock type compatibility matrix" Unclear
126672005-08-19
7:08
2005-09-14
6:38
MySQL Server: DocumentationClosed
(6770 days)
S3 Any"lock type compatibility matrix" still unclear
67472004-11-22
5:59
2004-11-30
11:58
MySQL Server: InnoDB storage engineClosed
(7058 days)
S24.1.7Linux (RedHat Enterprise Linux AS 3.0)Anyinnodb_locks_unsafe_for_binlog still uses next-key locking
70612004-12-07
2:53
2005-02-14
11:58
MySQL Server: InnoDB storage engineClosed
(6982 days)
S45.0.3-alpha-debugLinux (SUSE 9.2)AnyNo error message for ALTER with AUTO_INCREMENT
79752005-01-17
22:56
2005-04-18
10:22
MySQL Server: InnoDB storage engineClosed
(6919 days)
S34.1.9, official 686 binaryLinux (debian amd64 pure64)Anydeadlock without any locking, simple select and update
93542005-03-23
11:53
2005-06-01
15:57
MySQL Server: InnoDB storage engineClosed
(6875 days)
S24.1.10aWindows (WinXP Pro)AnyNext-key Locking doesn't allow the insert which does not produce phantom
102002005-04-27
9:54
2005-05-18
16:14
MySQL Server: InnoDB storage engineClosed
(6889 days)
S24.1.12, 5.0.6Linux (Linux)AnyUsing mysqldump to InnoDB tables causes error
126692005-08-19
8:48
2005-10-06
15:35
MySQL Server: InnoDB storage engineClosed
(6748 days)
S34.1.13Any (All)AnyCHECKSUM TABLE locks the InnoDB table, and does not use a consistent read
Showing all 10 (Edit, Save, CSV, Feed)