Bug #35252 MEMORY storage engine, non-unique keys
Submitted: 12 Mar 2008 18:29 Modified: 13 Mar 2008 10:09
Reporter: Philipp Kempgen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.x OS:Any
Assigned to: CPU Architecture:Any
Tags: Memory, storage engine, unique

[12 Mar 2008 18:29] Philipp Kempgen
Description:
The page at
http://dev.mysql.com/doc/refman/5.1/en/memory-storage-engine.html
says:
"You can have non-unique keys in a MEMORY  table."
while the same page in German
http://dev.mysql.com/doc/refman/5.1/de/memory-storage-engine.html
says:
"Es darf keine nicht-eindeutigen Schlüssel auf eine MEMORY-Tabelle geben."
(There *cannot* be any non-unique keys ...)
which is exactly the contrary.

How to repeat:
n/a
[12 Mar 2008 18:37] Philipp Kempgen
Suggested fix:
Edit the german page to read:
"Es darf nicht-eindeutige Schlüssel auf eine MEMORY-Tabelle geben."
(s/keine nicht-eindeutigen/nicht-eindeutige/)
- if that is correct.
[12 Mar 2008 19:34] Susanne Ebrecht
Verified as described ... 
Considering the mathematic rule: -1 * -1 = +1 then the translation from German in English only mean: you are allowed to use unique keys.

But there is a second bug in the German sentence:

You can have non-unique keys in a MEMORY  table. (This is an uncommon feature for implementations of hash indexes.)

Es darf keine nicht-eindeutigen Schlüssel auf eine MEMORY-Tabelle geben. (Dies ist ungebräuchlich für Implementierungen von Hash-Indizes.)

The word "ungebräuchlich" has a different meaning. Means: It's not possible to use instead of uncommon feature.

My translation suggestion:

Es können nicht-eindeutige Schlüssel bei Memory Tabellen verwendet werden. (Dies ist ein ungewöhnliches Feature für die Hash Index Implementierung).
[12 Mar 2008 19:47] Philipp Kempgen
Es können nicht-eindeutige Schlüssel bei Memory Tabellen verwendet werden.
(Dies ist ein ungewöhnliches Feature für Hash-Index-Implementierungen).
[13 Mar 2008 10:09] Stefan Hinz
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.