Bug #39926 Language should belong to client instead of server
Submitted: 8 Oct 2008 10:41 Modified: 8 Oct 2008 10:51
Reporter: Susanne Ebrecht Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: General Severity:S4 (Feature request)
Version:6.0 OS:Linux (Any)
Assigned to: CPU Architecture:Any
Triage: Triaged: D5 (Feature request)

[8 Oct 2008 10:41] Susanne Ebrecht
Description:
I worked on bug #7722 when I find the problem.

Imagine you neither will be able to speak French or German. But you have to use a database from France or Germany. You made a simple typo and will get:

mysql> creae table t(id serial);
ERROR 1064 (42000): Fehler in der SQL-Syntax. Bitte die korrekte Syntax im Handbuch nachschlagen bei 'creae table t(id serial)' in Zeile 1

or for the other database:

mysql> creae table t(id serial);
ERROR 1064 (42000): Erreur de syntaxe près de 'creae table t(id serial)' à la ligne 1

Do you think this is comfortable?

The same for persons who weren't able to speak/understand English with this error message:

mysql> creae table t(id serial);
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'creae table t(id serial)' at line 1

The setting of the language for error messages should be related to the client and not to the server. So that every user can choose his own language without interfere other users with other native languages here.

For software developers maybe it makes sense to have a separate output here for one language so that they can take the messages as they are and work with them.

Feature request summary:

1) Move language settings from server relation to client relation so that users will feel more comfortable

2) separate server messages in server language for software developers

How to repeat:
...

Suggested fix:
...