| Subject | RE: [firebird-support] Distributing/deploying Stored Procedures |
|---|---|
| Author | |
| Post date | 2015-03-14T08:27:02Z |
I should have qualified it a bit more (it sorts of says it in the header of the source)...
1) It only does non destructive updates,
It won't delete columns that no longer exits.
It wont rename columns
It wont transform data.
To do those things, you have to write your own script.
2) Don't run on production databases without backups and careful testing.
3) For distributed production update I would add a further "verification phase" after the updates had been run (this node version of the tool does not do this yet, my older closed source python version I use in production does).
If you get to know the tool and use it within its limitations, it can be quite effective, It saves me oodles of time.
1) It only does non destructive updates,
It won't delete columns that no longer exits.
It wont rename columns
It wont transform data.
To do those things, you have to write your own script.
2) Don't run on production databases without backups and careful testing.
3) For distributed production update I would add a further "verification phase" after the updates had been run (this node version of the tool does not do this yet, my older closed source python version I use in production does).
If you get to know the tool and use it within its limitations, it can be quite effective, It saves me oodles of time.