I haven't notice that because here's my 2 use cases :
big mail templates are used only in single language environnements (so the _Trl table is never read)
mail templates used in multi languages environnements are < 2K.
I've made the following test on Oracle (but I think result will be the same on PG) : Create a mail template with a text length > 2K -> Nothing is created in translation table ! (ORA-22835 - Buffer too small for CLOB to CHAR or BLOB to RAW conversion)
So I think R_MailText_Trl should also be updated (and data type must be identical). But also, each administrator should take a moment to check if data are consistent between 'master' and 'translation' tables
Nicolas
Carlos Ruiz February 26, 2019 at 5:12 PM
, just noticed that we changed R_MailText.MailText to a CLOB, but we didn't make the same change on R_MailText_Trl.
I haven't tested but I think it will bring issues for translations when the mail text is required to be bigger than 2K.
Hi Carlos,
I think you're right.
I haven't notice that because here's my 2 use cases :
big mail templates are used only in single language environnements (so the _Trl table is never read)
mail templates used in multi languages environnements are < 2K.
I've made the following test on Oracle (but I think result will be the same on PG) :
Create a mail template with a text length > 2K -> Nothing is created in translation table ! (ORA-22835 - Buffer too small for CLOB to CHAR or BLOB to RAW conversion)
So I think R_MailText_Trl should also be updated (and data type must be identical).
But also, each administrator should take a moment to check if data are consistent between 'master' and 'translation' tables
Nicolas