bug(replicator): error: insert or update on table "messages" violates foreign key constraint "messages_fid_foreign" about hub-monorepo HOT 6 CLOSED

I would say that if constraints are not respected, something odd happened. Removing constraint just remove control of data integrity.

I resynced from scratch my db.

I still have theses errors about constraints.

looking at this constraint:

constraint messages_fid_foreign
            references public.fids
            on delete cascade

It means that every message should have a corresponding fid in the fids table.
These message events are missing a fid in the database.
If I remove the constraint, I would have inconsistencies on joins between messages and other tables.

from hub-monorepo.

Linked: #1696, #1556.
Seems solvable by simple constraints removal.

from hub-monorepo.

I would say that if constraints are not respected, something odd happened. Removing constraint just remove control of data integrity.

I resynced from scratch my db.

I still have theses errors about constraints.

looking at this constraint:

constraint messages_fid_foreign
            references public.fids
            on delete cascade

It means that every message should have a corresponding fid in the fids table. These message events are missing a fid in the database. If I remove the constraint, I would have inconsistencies on joins between messages and other tables.

Indeed, I still experience same issue 3rd time (syncing from scratch as well) and agree that the linked issues provide rather a workaround and do not solve the actual problem.

from hub-monorepo.

One of the reasons we have some inconsistencies can be #1809

from hub-monorepo.

Calling out that this comment might help shed some light on what is being observed here. Appreciate your patience as we work through identifying a path forward.

from hub-monorepo.

Closing as we recommend using the Shuttle project instead of the old replicator (which has multiple issues).

from hub-monorepo.