You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but it didn't work properly, because we don't define any context, and contexts are registered as null in the database.
ref: https://stackoverflow.com/a/8289253
How about forcing users to define context, or set default context if it's not defined?
The text was updated successfully, but these errors were encountered:
kubosuke
changed the title
Kanta duplicates messages when deploying multiple application nodes
Kanta duplicates kanta_message records when context is null
Jun 30, 2024
but finally we decided to apply additional UNIQUE constraint to :domain_id, :msgid cause it's easier and it doesn't require to modify current kanta codes. but it'd be nice if we can apply default context if it's missing.
Environment
Overview
in our application, Kanta duplicates Message records and it causes unexpected behaviour.
as we investigate the behaviour, we found that unique constraint is defined at here:
kanta/lib/kanta/migrations/postgresql/v01.ex
Line 111 in 4df9af2
but it didn't work properly, because we don't define any context, and contexts are registered as
null
in the database.ref: https://stackoverflow.com/a/8289253
How about forcing users to define context, or set default context if it's not defined?
The text was updated successfully, but these errors were encountered: