ja: Fix mistranslation in SQL tuning section #305
Commits on Jul 18, 2019
-
ja: Fix mistranslation in "Tighten up the schema"
- Fix Japanese translation (the original translation doesn’t make sense)
-
ja: Fix mistranslation in "Tighten up the schema"
- Make Japanese translation more fluent
-
ja: Fix mistranslation in "Tighten up the schema"
- Fix Japanese mistranslation (the original Japanese translation means “Use INT for the numbers larger than 2^32 or 4 billion”.)
-
ja: Fix mistranslation in "Tighten up the schema"
- Fix Japanese mistranslation (the original Japanese translation means “this field often spends the largest size in RDBMS”.)
-
ja: Fix mistranslation in "Tighten up the schema"
- Fix Japanese mistranslation (the original Japanese translation means “Set the NOT NULL constraint where you can improve search performance”.)
-
ja: Fix mistranslation in "Use good indices"
- Fix Japanese mistranslation (the original Japanese translation means “Columns that you are retrieving with query (snip) could be faster with indices.”)
-
ja: Fix mistranslation in "Use good indices"
- Fix Japanese mistranslation (the original Japanese translation means “Columns that you are retrieving with query (snip) could be faster with indices.”)
-
ja: Fix mistranslation in "Use good indices"
- Fix Japanese translation (the original translation doesn’t make sense)
-
ja: Fix mistranslation in "Use good indices"
- Fix Japanese translation (“amount” is missing in the Japanese translation)
-
ja: Fix mistranslation in "Avoid expensive joins"
- Fix Japanese mistranslation (the original Japanese translation means “Denormalize where you need performance.”)
-
ja: Fix mistranslation in "Partition tables"
- Fix Japanese translation (the original translation doesn’t make sense)
-
ja: Fix mistranslation in "Source(s) and further reading: SQL tuning"
- Fix Japanese mistranslation (the original Japanese translation means “Is there a need to use so many VARCHAR(255)?”)
