Add a version column to the database, and integrate versioning with the UUID

Registered by Diana Graham on 2010-09-02

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://blueprints.launchpad.net/reformedchurcheslocator/+spec/versioning

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:
milestone icon 0.3.5
Started by
Douglas Huston on 2010-10-20
Completed by
Douglas Huston on 2010-10-20

Related branches

Sprints

Whiteboard

An example of how to create a database migration is here: http://caneypuggies.alwaysreformed.com/wiki/DevelopingWithMigrations

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.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.