sudr / dbdeploy

Automatically exported from code.google.com/p/dbdeploy
0 stars 0 forks source link

Apply changes directly to the database. #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
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.

Original issue reported on code.google.com by akn...@gmail.com on 1 Mar 2009 at 11:38

GoogleCodeExporter commented 9 years ago
This would greatly simplify use of dbdeploy for most users, and would be a very 
good
feature to add.

Original comment by gtack...@googlemail.com on 11 Mar 2009 at 9:54

GoogleCodeExporter commented 9 years ago

Original comment by gtack...@googlemail.com on 11 Mar 2009 at 9:58

GoogleCodeExporter commented 9 years ago
This should be in release 3.0.

Original comment by gtack...@googlemail.com on 15 Mar 2009 at 6:00

GoogleCodeExporter commented 9 years ago
Implemented in r110.

Need to update GettingStarted (and probably other docs too) to reflect this 
change.

Original comment by gtack...@googlemail.com on 11 Oct 2009 at 4:41

GoogleCodeExporter commented 9 years ago

Original comment by gtack...@googlemail.com on 11 Oct 2009 at 4:41

GoogleCodeExporter commented 9 years ago

Original comment by gtack...@googlemail.com on 11 Oct 2009 at 4:43

GoogleCodeExporter commented 9 years ago
Docs updated

Original comment by gtack...@googlemail.com on 18 Oct 2009 at 8:41