MySQL 4.1.0 crash every running with tis620 charset

Hi.
 
With MySQL 4.1.0 alpha when I try to set default character set to tis620
MySQL start OK but have crash every time when perform to run query (with
default_character_set=latin1 it never got error) and with MySQL 4.0.14 it
can do with out any error. The query just so simple like "show variables"
 
Thanks
Kittiphum Worachat.

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org
Kittiphum Worachat [ Fr, 01 August 2003 04:45 ] [ ID #76125 ]

Re: MySQL 4.1.0 crash every running with tis620 charset

Hello,

Kittiphum Worachat wrote:
> Hi.
>
> With MySQL 4.1.0 alpha when I try to set default character set to tis620
> MySQL start OK but have crash every time when perform to run query (with
> default_character_set=latin1 it never got error) and with MySQL 4.0.14
> it can do with out any error. The query just so simple like "show
> variables"

I was able to repeat crash, but in a different way.

mysqld crashes on any qyery which comes from *client* started with tis620 no
matter what default mysqld character set in.

Can you check if this si the case with your setup?

Start mysqld with latin1
connect with

mysql --default-character-set=tis620

mysqld crashes.


> Thanks
> Kittiphum Worachat.

Best regards


--
Are you MySQL certified? -> http://www.mysql.com/certification
For technical support contracts, visit https://order.mysql.com/?ref=msal
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Alexander Keremidarski <salle [at] mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Sofia, Bulgaria
<___/ www.mysql.com




--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org
Alexander Keremidarsk[1] [ Fr, 01 August 2003 11:47 ] [ ID #76126 ]
Datenbanken » gmane.comp.db.mysql.bugs » MySQL 4.1.0 crash every running with tis620 charset

Vorheriges Thema: field name:errors
Nächstes Thema: mysql_bind_result does not support BLOB fields