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
{{ message }}
This repository was archived by the owner on Sep 18, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 18, 2026. It is now read-only.
Core (PR #11256):
No unique constraint. Multiple rows per room+type are normal for updates.
Why we have it:
We originally tried to store awareness (one row per room) and updates (many rows per room) in the same table. The UNIQUE constraint allows multiple NULL type values (MySQL quirk) but only one non-NULL value per room.
Fixed in commit. Removed UNIQUE KEY room_type constraint from schema. With composite storage (Presence API for awareness, wp_collaboration for CRDT only), this constraint is unnecessary and could prevent legitimate multi-update scenarios.
Activity
josephfusco commentedon Aug 17, 2026
Fixed in commit. Removed UNIQUE KEY room_type constraint from schema. With composite storage (Presence API for awareness, wp_collaboration for CRDT only), this constraint is unnecessary and could prevent legitimate multi-update scenarios.
Schema after fix:
No more UNIQUE constraint. Verified with
SHOW CREATE TABLEafter fresh activation.