Bug #9123 | mysqldump database member_opinion | ||
---|---|---|---|
Submitted: | 11 Mar 2005 9:33 | Modified: | 17 Mar 2005 16:33 |
Reporter: | Bernhard Graf | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
Version: | 4.1.10 | OS: | Linux (Linux (presumably all)) |
Assigned to: | Lars Thalmann | CPU Architecture: | Any |
[11 Mar 2005 9:33]
Bernhard Graf
[15 Mar 2005 15:23]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/23042
[16 Mar 2005 12:48]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/23086
[16 Mar 2005 13:16]
Lars Thalmann
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bugfix, yourself. More information about accessing the source trees is available at http://www.mysql.com/doc/en/Installing_source_tree.html Additional info: Will be part of 4.1.11 and 5.0.3 releases.
[16 Mar 2005 20:57]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/23112
[17 Mar 2005 13:00]
Lars Thalmann
Should be added to documentation too...
[17 Mar 2005 16:33]
Paul DuBois
Noted in 4.1.11, 5.0.3 changelogs.