24.01.2017 21:21, kragh.tho...@yahoo.com [firebird-support] wrote:
> could you please elaborate on your point of view?
>
> What can go wrong during this kind of operation?
Upgrade script may fail and you database will end up in half-upgraded state.
It could
be simpler to restore fresh-made
Dimitry, could you please elaborate on your point of view? What can go wrong
during this kind of operation? Is there a risk of database/backup corruption?
---In firebird-support@yahoogroups.com, wrote :
24.01.2017 13:47, kragh.thomas@... mailto:kragh.thomas@...
24.01.2017 13:47, kragh.tho...@yahoo.com [firebird-support] wrote:
> To be clear when the change scripts is applied to production they have been
> tested on our
> CI server and in our pre-prod environment.
> We have been using this way of updating our schema for a few years now and it
> works
Thanks for the reply's To be clear when the change scripts is applied to
production they have been tested on our CI server and in our pre-prod
environment. We also uses the same pattern as Sean described, where script
files are numbered and applied in the correct order
On 24/01/2017 01:03, 'Leyne, Sean' s...@broadviewsoftware.com
[firebird-support] wrote:
Firebird does support dynamic changes, you can change the database
schema while users are connected.
Dmitry was referring more to the inherent risks of using a production
database as a development