#1036 - Localise translate table
-
By Chris Graham
- Added
- 6 views
| Identifier | #1036 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Localise translate table |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | core |
| Description | If the user is not wanting content-translation support, we can remove the translate table, embedding fields for Comcode direct into normal tables.
We would do this by re-coding all APIs to be able to dynamically target both database configurations: separate table, and specially embedded extra fields. It would all be automated within the APIs, including: - Table creation (which would have to create fulltext indexing as well as additional 'magic' fields) - insert_lang / lang_remap / delete_lang - get_translated_text / get_translated_tempcode - any hard-coded translate joins would need to go through an API layer now Advantages: - Easier to understand for manual database editing - Easier for programmers writing unofficial code who want to write simple queries - Easier to work with (e.g. change synching) - Easier to partition for scalability - Better MySQL performance (less monolithic indexing) - Better fulltext search performance (significantly reduced join misses) |
| Steps to reproduce | |
| Related to | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments