Add a version column to the database, and integrate versioning with the UUID
Add a version column to the database, and integrate versioning with the UUID so one UUID can have multiple rows in the database, where each row is for a unique version of that UUID. Read the "versioning" blueprint for more context: https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Douglas Huston
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
-
0.3.5
- Started by
- Douglas Huston
- Completed by
- Douglas Huston
Related branches
Related bugs
Sprints
Whiteboard
An example of how to create a database migration is here: http://
TODO:
- Do we need to record a globally unique ID for each version beyond simply recording its UTC creation date? I don't think so. So, uniquely identify each version by its UTC date/time.
- Create these new columns in the model:
- uuid # this records the unique congregation or group
- creation_date # this records the version of this UUID's unique congregation or group
- Create and run a database migration to make the above changes to the database
Work Items
Dependency tree
* Blueprints in grey have been implemented.
