vervis/migrations/431_2022-08-30_collab_loom.model

Loom

Collab

CollabTopicLocal
    collab CollabId

    UniqueCollabTopicLocal collab

CollabTopicLocalLoom
    collab    CollabId
    collabNew CollabTopicLocalId
    loom      LoomId

    UniqueCollabTopicLocalLoom collab
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 17:28:44 +09:00			`Loom`

			`Collab`

			`CollabTopicLocal`
			`collab CollabId`

			`UniqueCollabTopicLocal collab`

			`CollabTopicLocalLoom`
			`collab CollabId`
			`collabNew CollabTopicLocalId`
			`loom LoomId`

			`UniqueCollabTopicLocalLoom collab`