forge/Vervis
1
0
Fork 0
Code Pull requests Activity
Vervis/migrations/451_2022-08-30_collab_remote_accept.model

7 lines
178 B
Text
Raw Normal View History

DB: Separate tables for CollabTopicLocalAccept and CollabTopicRemoteAccept Previously there was just CollabTopicAccept, which worked only for local topics but pretended to apply to both, due to directly pointing to Collab, thus possible to insert rows even if there's a CollabTopicRemote. The new situation is a new CollabTopicLocal table to which the local topic things point, thus keeping the local and remote data separate and difficult to confuse.
2022-08-30 10:28:44 +02:00
CollabTopicRemoteAccept
collab CollabTopicRemoteId
accept RemoteActivityId
UniqueCollabTopicRemoteAcceptCollab collab
UniqueCollabTopicRemoteAcceptAccept accept
Copy permalink