Myles Wakeham wrote:

> We have a vertical market product that we are converting to Firebird. The
> database environment it is being converted from automatically handles
> changes to the schema of the database from version to version, however I
> suspect that we will have to do this ourselves with Firebird.
>
> I would like to know, from other vertical market developers who are using
> Firebird, how they are handling changes in the SQL Schemas when releasing
> updates of their software to their customers? Are there any tools that make
> this process easy to do, or do you have to write this yourself?

If a structural change is made, the a new blank database is supplied,
along with scripts to copy from the old database to the new. If any
copies fail, then the problem is noted, and sorted before trying again.
We usually get a few niggles relating to mistakes in the old copy, so
they get picked up. Once happy with the new database THEN you switch
over. Often they run a few days of tests with the new setup, then do a
clean switch the following weekend - with a clean upload.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services