Database Migrations
Reported by Paul Jones | July 20th, 2011 @ 10:39 AM
To prevent needing to delete and recreate the configuration store each time we mess with the database, we should support migrations to update the database.
Comments and changes to this ticket
-
Ben Hood July 20th, 2011 @ 10:40 AM
(from [54a0f4f9f7c65fe734c12ae196d7d8a7cecd64ca]) [#303] Add ability to upgrade database. https://github.com/lshift/diffa/commit/54a0f4f9f7c65fe734c12ae196d7...
-
Paul Jones July 20th, 2011 @ 10:43 AM
- Assigned user changed from “Paul Jones” to “Ben Hood”
- State changed from “open” to “resolved”
Pull Request raised for merge into 301 (which provides the first interesting upgrade task), and can subsequently be merged into master with 301's merge.
-
Ben Hood July 20th, 2011 @ 11:42 AM
- State changed from “resolved” to “closed”
Looks good - I've merged this into #301 -> QA+
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood