Subject Re: [firebird-support] Handling version control
Author Lucas Franzen

I do have a table that holds the current version (and other database
related info).

The program itself can handle multiple versions. By using const for the
DBVersions the program can "decide" what to do at certain situations (ie
disable functions that won't work from a certain version on, use
different SQL statements, etc.);
Declaring the consts has also the nice effect that you can clean up your
code more easily if a versions runs out to be from interest (garbage
collection *g*).
So you can easily prohibit working with inappropriate versions of the
database and client app.

To update the database I use a separate program that has TIB_Scripts (I
use IBO) that holds all the DDL for each version.

Works perfectly at all sites for years.