Range Use Plan versioning #56
Description
Range use plans are living documents and knowing what state they were in at any point time is going to be important moving forward. Locking down past versions from erroneous updates (like the FTA data push) will be critical as well.
It looks like versioning was at least thought about during dev and when you update a plan record its id changes (which is odd). Could be that a new record is getting created and the old one purged. A better solution will be to add a version column to both the plan object and its children. Some data duplication is expected but given the small data sets we are dealing with it's a non issue.
This issue is to track the work on adding versioning to the api, there will be separate issues for range-web and range-ios.