| Issue 10: | Apply changes directly to the database. | |
| 2 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
As an application author, I want to apply any necessary change scripts to the database by invoking DBDeploy from code, so that I can easily reset my database between tests. Acceptance criteria: * After invoking dbdeploy, any necessary scripts must have been actually applied to the database. * I should not have to duplicate any dbdeploy code in order to invoke it from my application. This may really be 2 stories? Proposal: Overload ToPrintSteamDeployer.doDeploy(), to allow injection of a ChangeScriptWriter, for which the application author can substitute an implementation that writes changes direct to the database. DBDeploy should be the facade through which the application author injects the substitute ChangeScriptWriter. |
||||||||||||||||
,
Mar 11, 2009
This would greatly simplify use of dbdeploy for most users, and would be a very good feature to add.
Owner: gra...@tackley.net
Labels: Type-Enhancement Priority-High Component-Core Component-CLI Component-Ant Component-Docs |
|||||||||||||||||
,
Mar 11, 2009
(No comment was entered for this change.)
Status: Accepted
|
|||||||||||||||||
,
Mar 15, 2009
This should be in release 3.0.
Labels: -Priority-High Priority-Critical Milestone-Release3.0
|
|||||||||||||||||
,
Oct 11, 2009
Implemented in r110. Need to update GettingStarted (and probably other docs too) to reflect this change.
Labels: -Component-Core -Component-Ant
|
|||||||||||||||||
,
Oct 11, 2009
(No comment was entered for this change.)
Status: Started
|
|||||||||||||||||
,
Oct 11, 2009
(No comment was entered for this change.)
Labels: -Milestone-Release3.0 Milestone-Release3.0M2
|
|||||||||||||||||
,
Oct 18, 2009
Docs updated
Status: Done
|
|||||||||||||||||
|
|
|||||||||||||||||