Showing all 15 (Edit, Save, CSV, Feed)
ID# Date Type Status Sev Version Target OS Summary Assigned
230322006-10-06
1:00
Server: SPVerified
(348 days)
S35.0.24aMac OS X (Mac OS X.4)Handlers declared in a SP do not handle warnings generated in sub-SP Davi Arnaut
313542007-10-02
22:30
Server: GeneralVerifiedS35.0.46AnyMySQL binds to port while executing init_file  
365692008-05-07
17:32
Server: OptimizerPatch pending
(348 days)
S55.0.56sp1AnyUPDATE ... WHERE ... ORDER BY... always does a filesort even if not required Gleb Shchepa
428062009-02-12
22:20
Connector/ODBC: DocsDocumenting
(258 days)
S23.51.27Sun SolarisInstallation of Connector/ODBC refers to non-existant files Tony Bedford
438592009-03-25
16:08
Server: GeneralVerifiedS35.0/5.1Microsoft Windows (64-bit)64-bit Windows variables limited to different values than 64-bit Linux/Solaris  
447482009-05-08
14:56
Monitoring: AgentVerifiedS32.0.5.7153AnyAgent does not identify the instance in error messages MEM Agent Devs
452172009-05-31
16:25
Server: MyISAMVerified
(177 days)
S35.1.325.4+AnyUsing myisamchk --unpack results in small myisam_data_pointer_size  
454152009-06-09
22:17
Server: PackagingVerifiedS35.1.345.1+Linux (Red Hat/SUSE)rpm upgrade recreates test database Joerg Bruehe
460182009-07-07
21:16
Server: GeneralDocumenting
(4 days)
S35.0,5.15.4+Anygroup_concat(distinct ...) uses max_heap_table_size for memory allocations Alexey Botchkov
471472009-09-04
23:17
ClientPatch approved
(60 days)
S35.1Anymysql client option --skip-column-names does not apply to vertical output Jim Winstead
483302009-10-26
22:47
Server: DocsVerifiedS3AnyReplication SSL page incorrect refers to using server-cert's on the slave Paul DuBois
486072009-11-06
20:15
Server: InnoDBVerifiedS35.1+AnyREAD UNCOMMITTED uses more locks than READ COMMITTED in InnoDB 5.1+ Marko Mäkelä
488482009-11-17
21:00
Server: MyISAMVerifiedS25.1.40Anymyisamchk doing sort recover in certain cases resets data pointer to small size  
490012009-11-23
21:29
Server: InnoDBVerifiedS35.0,5.1,5.1 with pluginAnySHOW INNODB STATUS deadlock info incorrect when deadlock detection aborts Jimmy Yang
490472009-11-24
18:55
Server: InnoDBVerifiedS55.0,5.1,pluginAnyInnoDB deadlock detection is CPU intensive with many locks on a single row  
Showing all 15 (Edit, Save, CSV, Feed)