|
|
41.
|
|
|
When repairing table {1}… {2} = {3}
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TABLE_FIXED
|
|
|
42.
|
|
|
Website cleanup tools
|
| Context: |
|
[strings]MODULE_TRANS_NAME_admin_cleanup
|
|
|
|
|
Veebilehe puhastamise tööriistad
|
|
Translated and reviewed by
olavi tohver
|
|
|
|
Located in
[strings]MODULE_TRANS_NAME_admin_cleanup
|
|
|
43.
|
|
|
Correct MySQL schema issues
|
|
|
|
|
Korrasta MySQL andmebaasiskeemi probleemid
|
|
Translated and reviewed by
Timo Tambet
|
|
|
|
Located in
[strings]CORRECT_MYSQL_SCHEMA_ISSUES
|
|
|
44.
|
|
|
Programmers will often make changes to MySQL databases manually, but this disadvantages the software because properly written code will create additional structural meta-data in the database that is used to provide a rich cross-platform way to query the database (used by the backup system, as well as broken image checking, and various other features). This tool will identify missing schema data and fill in the blanks; it cannot identify exact types so will try and intelligently guess and show the results.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]DESCRIPTION_CORRECT_MYSQL_SCHEMA_ISSUES
|
|
|
45.
|
|
|
The following query was executed to fix the database: <code>{1}</code>
|
|
|
|
|
Järgnev päring on käivitatud, et parandada andmebaasi: <code>{1}</code>
|
|
Translated and reviewed by
Timo Tambet
|
|
|
|
Located in
[strings]MYSQL_QUERY_CHANGES_MADE
|
|
|
46.
|
|
|
No MySQL schema changes were required.
|
|
|
|
|
MySQL andmebaasiskeemi muutusi ei nõutud.
|
|
Translated and reviewed by
Timo Tambet
|
|
|
|
Located in
[strings]NO_MYSQL_QUERY_CHANGES_MADE
|
