Fresh Database is initialiased with wrong schema version
Reported by Paul Jones | 2011-07-21 16:54:35 UTC
When a fresh DB config is created, the schemaVersion is set to 0. This is no longer the latest version, and it should instead track the latest migration version.
Comments and changes to this ticket
-
Paul Jones 2011-07-21 17:10:04 UTC
- Assigned user changed from “Paul Jones” to “Ben Hood”
- State changed from “open” to “resolved”
Ready for QA.
-
Ben Hood 2011-07-21 17:10:08 UTC
(from [5e00c91b64b7c5b9e1a9469c58fc2db6f45d0d8e]) [#309] Apply the latest schema version to newly created schemas. https://github.com/lshift/diffa/commit/5e00c91b64b7c5b9e1a9469c58fc...
-
Ben Hood 2011-07-21 17:23:02 UTC
(from [764b237fd4b04cc4c6c38a15905cb571ba5695d6]) Merge pull request #49 from lshift/309
[#309] Apply the latest schema version to newly created schemas. https://github.com/lshift/diffa/commit/764b237fd4b04cc4c6c38a15905c...
-
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