View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 1036 | Composr | core | public | 2013-02-12 12:53 | 2014-09-02 22:44 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 1036: Localise translate table | ||||
| 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) | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 40 | ||||
| Sponsorship open | |||||
| related to | 970 | Resolved | Chris Graham | Better support for negated search results |
