New issue report by olivier.oswald:
Extend the code to support versioning a database by module.
Consider an application that consists of a core code base which can be
extended by modules such as add-ons or plugins. Each module maintains its
own part of the database with its own migration assembly.
This is tricky as module versions usually depend on specific core versions
(or even other modules):
[Migration("Inventory", 5)]
[DependsOn("Core", 7)]
[DependsOn("AssetLibrary", 3)]
public class Migration005 : Migration {
}
Issue attributes:
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings