Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
jvx:client:model:databook:recordtranslation [2020/06/08 15:41] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:client:model:databook:recordtranslation [2020/06/15 10:15] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
---|---|---|---|
Line 2: | Line 2: | ||
~~Title: Record Translation~~ | ~~Title: Record Translation~~ | ||
- | Sometimes it's important to translate records of a table/data book. If you have such a requirement, you can use different solutions: | + | Sometimes it's important to translate records of a table/databook. If you have such a requirement, you can use different solutions: |
* Use a view and translate column values via database | * Use a view and translate column values via database | ||
* Translate values on the client (without database) | * Translate values on the client (without database) | ||
- | If you choose the first option, everything will be fine because it'll be possible to use filtering and searching via database. With second option, only client-side filtering and searching will work. //Why?// | + | If you choose the first option, everything will be fine because it'll be possible to use filtering and searching via database. With the second option, only client-side filtering and searching will work. //Why?// |
If you translate, for example, English content to German on the client side, the value in the database is still English. If the user tries to search a German value, the database won't find it because all values are in English. | If you translate, for example, English content to German on the client side, the value in the database is still English. If the user tries to search a German value, the database won't find it because all values are in English. |