Bug #15978 Charset support for cluster under Solaris
Submitted: 25 Dec 2005 21:27 Modified: 23 Mar 2006 8:35
Reporter: Serge Kozlov Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0.17 OS:Solaris (Solaris 10 (Sparc 64))
Assigned to: CPU Architecture:Any

[25 Dec 2005 21:27] Serge Kozlov 
Description:
There is a test suite that covers all charset/collations for MyISAM, InnoDB, Memory and NDB. In fact same test code used for all engines. But under Solaris (and for some Linux machines) testing of charsets for NDB produces errors. 

How to repeat:
Following query returns the error message in testcase :

CREATE TABLE test.t1 (a VARCHAR(3) CHARACTER SET armscii8 COLLATE armscii8_bin) ENGINE=NDB CHARACTER SET armscii8 COLLATE armscii8_bin' failed: 1005: Can't create table './test/t1.frm' (errno: 743)

If change engine to MyISAM/InnoDB/Memory then all work fine.
[8 Jan 2006 15:45] Hartmut Holzgraefe 
~ > perror --ndb 743
OS error code 743:  Unsupported character set in table or index: Permanent error: Schema error

what does the configure string look like for this test case?
[10 Jan 2006 15:27] Serge Kozlov 
./mysql-test-run.pl --suite=funcs_2
[23 Feb 2006 8:35] Valeriy Kravchuk 
Have you used MySQL's binary distribution or just built from sources yourself? In the later case, please, send the exact configure command line used. Have your tried to repeat with the newer version, 5.0.18?
[24 Mar 2006 0:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".