With GBAK restore function we used to have
-c[reate_database] - Restore database to a new file
and
-r[eplace_database] - Restore database to a new file or replace existing

I understood these options - I'd never use the -r option because I would
never replace an existing database.

Now we have:
-C(REATE_DATABASE) create database from backup file
-R(ECREATE_DATABASE) [O(VERWRITE)] create (or replace if OVERWRITE used)
database from backup file
-REP(LACE_DATABASE) replace database from backup file


The release notes are a litle confusing:
"• gbak -R (or gbak -r) now applies to the new -R[ECREATE_DATABASE] switch
and will never overwrite
an existing database if the O[VERWRITE] argument is absent
• The short form of the old gbak -R[EPLACE_DATABASE] is now
-REP[LACE_DATABASE]. This switch
does not accept the O[VERWRITE] argument.
• The -REP[LACE_DATABASE] switch should be considered as deprecated, i.e. it
will become unavailable
in some future Firebird release.
This change means that, if you have any legacy batch or cron scripts that
rely on “gbak -r” or “gbak -R” without modification, then the operation will
except if the database exists.
If you want to retain the ability of your script to overwrite your database
unconditionally, you will need to
modify the command to use either the new switch with the OVERWRITE argument
or the new short form for
the old -REPLACE_DATABASE switch."

This states that -REP is deprecated. But it is NEW?
Why did we introduce a new switch and deprecate it?
Introducing the O switch was enough wasn't it?

 regards
 Alan McDonald