Introduce schema version as a separate table
Reported by Ben Hood | July 28th, 2011 @ 08:49 AM
ATM the schema version property is stored persistently in the ConfigOptions table, which makes this susceptible to changes in that table. Introducing this simple individual, there is very little chance that the concrete storage of the schema version property would ever have to get refactored.
Comments and changes to this ticket
-
Ben Hood July 28th, 2011 @ 09:42 AM
(from [c5774e4651384fbf62a68b4f514a47089f15a7b8]) [#315] Add version to DB schema https://github.com/lshift/diffa/commit/c5774e4651384fbf62a68b4f514a...
-
Ben Hood July 28th, 2011 @ 09:46 AM
- Assigned user changed from “Ben Hood” to “Paul Jones”
- State changed from “new” to “resolved”
PR raised for this ticket -> resolving
-
Ben Hood July 28th, 2011 @ 01:36 PM
(from [1146368aab8c840c46dd1e51a7702ae9f6b6e9a8]) [#315] Addressed some QA remarks https://github.com/lshift/diffa/commit/1146368aab8c840c46dd1e51a770...
-
-
-
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