forge/Vervis
1
0
Fork 0
Code Pull requests Activity
Vervis/migrations/2016_08_04.model

197 lines
3.8 KiB
Text
Raw Normal View History

Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
-- This file is part of Vervis.
--
-- Written in 2016 by fr33domlover <fr33domlover@riseup.net>.
--
-- ♡ Copying is an act of love. Please copy, reuse and share.
--
-- The author(s) have dedicated all copyright and related and neighboring
-- rights to this software to the public domain worldwide. This software is
-- distributed without any warranty.
--
-- You should have received a copy of the CC0 Public Domain Dedication along
-- with this software. If not, see
-- <http://creativecommons.org/publicdomain/zero/1.0/>.
-------------------------------------------------------------------------------
-- People
-------------------------------------------------------------------------------
Sharer
ident ShrIdent
name Text Maybe
Switch from persistent-parser to my own parser module My parser doesn't support default=, and I think it's safe to assume nobody is running an instance whose DB schema version is one of those first 5 where default= exists, so I'm remvoing it from the original 2016 model file. The unset-default migrations remain, and I checked in `psql` that PostgreSQL accepts the operation on columns that don't have a default value. If it turns out to be a problem, I can replace those migrations with no-op ones.
2019-05-07 02:58:44 +02:00
created UTCTime
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
UniqueSharer ident
Person
ident SharerId
login Text
hash Text Maybe
email Text Maybe
UniquePersonIdent ident
UniquePersonLogin login
SshKey
ident KyIdent
person PersonId
algo ByteString
content ByteString
UniqueSshKey person ident
Group
ident SharerId
UniqueGroup ident
GroupMember
person PersonId
group GroupId
role GroupRole
joined UTCTime
UniqueGroupMember person group
RepoRole
ident RlIdent
sharer SharerId
desc Text
UniqueRepoRole sharer ident
RepoRoleInherit
parent RepoRoleId
child RepoRoleId
UniqueRepoRoleInherit parent child
RepoAccess
role RepoRoleId
op RepoOperation
UniqueRepoAccess role op
RepoCollab
repo RepoId
person PersonId
role RepoRoleId
UniqueRepoCollab repo person
RepoCollabAnon
repo RepoId
role RepoRoleId
UniqueRepoCollabAnon repo
RepoCollabUser
repo RepoId
role RepoRoleId
UniqueRepoCollabUser repo
ProjectRole
ident RlIdent
sharer SharerId
desc Text
UniqueProjectRole sharer ident
ProjectRoleInherit
parent ProjectRoleId
child ProjectRoleId
UniqueProjectRoleInherit parent child
ProjectAccess
role ProjectRoleId
op ProjectOperation
UniqueProjectAccess role op
ProjectCollab
project ProjectId
person PersonId
role ProjectRoleId
UniqueProjectCollab project person
ProjectCollabAnon
repo ProjectId
role ProjectRoleId
UniqueProjectCollabAnon repo
ProjectCollabUser
repo ProjectId
role ProjectRoleId
UniqueProjectCollabUser repo
-------------------------------------------------------------------------------
-- Projects
-------------------------------------------------------------------------------
Project
ident PrjIdent
sharer SharerId
name Text Maybe
desc Text Maybe
Switch from persistent-parser to my own parser module My parser doesn't support default=, and I think it's safe to assume nobody is running an instance whose DB schema version is one of those first 5 where default= exists, so I'm remvoing it from the original 2016 model file. The unset-default migrations remain, and I checked in `psql` that PostgreSQL accepts the operation on columns that don't have a default value. If it turns out to be a problem, I can replace those migrations with no-op ones.
2019-05-07 02:58:44 +02:00
nextTicket Int
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
wiki RepoId Maybe
UniqueProject ident sharer
Repo
ident RpIdent
sharer SharerId
Switch from persistent-parser to my own parser module My parser doesn't support default=, and I think it's safe to assume nobody is running an instance whose DB schema version is one of those first 5 where default= exists, so I'm remvoing it from the original 2016 model file. The unset-default migrations remain, and I checked in `psql` that PostgreSQL accepts the operation on columns that don't have a default value. If it turns out to be a problem, I can replace those migrations with no-op ones.
2019-05-07 02:58:44 +02:00
vcs VersionControlSystem
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
project ProjectId Maybe
desc Text Maybe
Switch from persistent-parser to my own parser module My parser doesn't support default=, and I think it's safe to assume nobody is running an instance whose DB schema version is one of those first 5 where default= exists, so I'm remvoing it from the original 2016 model file. The unset-default migrations remain, and I checked in `psql` that PostgreSQL accepts the operation on columns that don't have a default value. If it turns out to be a problem, I can replace those migrations with no-op ones.
2019-05-07 02:58:44 +02:00
mainBranch Text
Complete DB migration list, allowing to upgrade 2016-08-04 running instance Until now the list of DB migration actions was incomplete, containing only changes made since I added the migration system itself. It now contains the 2016-08-04 model, and then every change made since then. IMPORTANT: The 2016-08-04 instance doesn't have a schema version entity at all, so it is assigned version 0, while the actual version of its schema is 1. I'm going to patch persistent-migration to allow it to be 1, making the migration path smooth.
2018-03-27 16:28:56 +02:00
UniqueRepo ident sharer
Ticket
project ProjectId
number Int
created UTCTime
creator PersonId
title Text
desc Text -- Assume this is Pandoc Markdown
assignee PersonId Maybe
done Bool
closed UTCTime
closer PersonId
discuss DiscussionId
UniqueTicket project number
TicketDependency
parent TicketId
child TicketId
UniqueTicketDependency parent child
TicketClaimRequest
person PersonId
ticket TicketId
message Text -- Assume this is Pandoc Markdown
created UTCTime
UniqueTicketClaimRequest person ticket
Discussion
nextMessage Int
Message
author PersonId
created UTCTime
content Text -- Assume this is Pandoc Markdown
parent MessageId Maybe
root DiscussionId
number Int
UniqueMessage root number
Copy permalink