Bug #14918 NDB storage node RPM missing charset files
| Submitted: | 14 Nov 2005 11:06 | Modified: | 1 Aug 2006 1:03 |
|---|---|---|---|
| Reporter: | Hartmut Holzgraefe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
| Version: | 4.1.15 | OS: | Linux (linux) |
| Assigned to: | Kent Boortz | CPU Architecture: | Any |
[14 Nov 2005 11:06]
Hartmut Holzgraefe
[10 May 2006 20:41]
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/commits/6223
[25 Jul 2006 22:00]
Hartmut Holzgraefe
Works fine with --extra-charsets=all ndbd can handle all charsets even without having access to the charset Index.xml and no error messages or warnings are produced in any of the logs
[25 Jul 2006 22:12]
Kent Boortz
The change was introduced in 4.1.21, 5.0.23 and 5.1.11-beta
[1 Aug 2006 1:06]
Jon Stephens
Documented in the 4.1.21/5.0.23/5.1.11 changelogs as follows: "NDB Cluster: A Cluster whose storage nodes were installed from the MySQL-ndb-storage-* RPMs could not perform CREATE or ALTER operations that made use of non-default character sets or collations."
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.062 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.