#1795 Problems with german umlaute within error messages.

[Anonymous]

Originally created by: manfred-...@t-online.de

What exact steps will reproduce the problem?
1. create table ElternT (eNr integer not null, primary key (eNr))
   engine = InnoDB;
2. create table KinderT (kNr integer not null, primary key (kNr),
                         ENr integer,
   foreign key (ENr) references ElternT (eNr)) engine = InnoDB;
3. insert into KinderT (kNr, ENr) values (1, 1);
Because of the missing parents, the insert causes an error, that's clear.
The following german error message is displayed in a window:
--------------------------------------------------------------------------
SQL Error (1452): Kann Kind-Zeile nicht hinzufgen oder aktualisieren: eine
Fremdschlsselbedingung schlgt fehl
("xxx"."kindert", CONSTRAINT "kindert_ibfk_1" FOREIGN KEY ("ENr")
REFERENCES "elternt" ("eNr"))
--------------------------------------------------------------------------
As you can see, the german umlaute äöü are missing.
This is my problem!
My errmsg.sys contains the correct text.
The first missing ü in "hinzufgen" is hex FC in errmsg.sys.

Version used?
HeidiSQL revision: 5.0.0.3168
MySQL Server version: 5.1.38-community
Operating system: Windows XP SP2

[Anonymous]

Originally posted by: a...@anse.de

Sounds like some Unicode issue.

If I want to use german messages to reproduce that, what do I have to set up in my
my.ini?

Labels: Severity-Cosmetic
Status: Accepted

[Anonymous]

Originally posted by: manfred-...@t-online.de

You need the file share/german/errmsg.sys
and the following entry in my.ini in the section [mysqld]:
language = german

[Anonymous]

Originally posted by: a...@anse.de

Thanks, I'll check that.

[Anonymous]

Originally posted by: a...@anse.de

Strange. I get correct chars when I'm just executing 'äöü':
"Fehler in der SQL-Syntax. Bitte die korrekte Syntax im Handbuch nachschlagen bei
'äöü' in Zeile 1"
Only if the message itself, not the query part has umlauts, this is broken. Looks
like the server breaks that, not the client. Same results when using mysql.exe
command line client. Report that to bugs.mysql.com ?

Status: Upstream