With the last deployment of our ng client application, the new i18n entries did not get inserted into the i18n messages table.
In the Servoy log file, we find the following error:
… message_id cannot be null…
It seems, as if the records should be inserted with an id of null instead of a valid Servoy sequence.
I created an i18n table called i18n_teacher_messages in developer. PK became message_id by Servoy.
When deploying the NG’s WAR file, the i18n table is created and the PK is i18n_teacher_messagesid (the Wiki says, it should be <table_name>_id).
Any future changes to i18n are not reflected in production.
After another effort with a new i18n table and new deployments with changes in i18n, the problem disappeared (for now).
We have no idea, what the differences are to all the other version we deployed.
Anyway, we are still interested in similar experiences.