Work was resumed and completed on this tricky feature for the 1.5 client and varchars now cross the wire right-trimmed to actual length plus two bytes.

Now you can write conditional insert/update/delete actions in one Before or After trigger to have the one trigger cover all DML actions for that trigger's phase. This cuts down the composition and maintenance of triggers without deprecating the ability to have multiple triggers per phase.

Indexes that enforce named integrity constraints may now be named with user-defined identifiers.

Now-in both Release 1.0 and this release-the maximum number of indexes you can define for a table has been increased from 64 to 256.

For the rare times when you need to impose a pessimistic lock, this release adds syntax to place a “reader's lock” on rows as they are output to the client. Use with care.

Connection to the security database is cached in Superserver builds. It means that security.fdb is loaded when the first connection is made and stays attached until all client connections are gone.

Where possible, error messages report the cause of SQL errors at a more detailed level. It is IMPORTANT to note that you will encounter bizarre messages if you use an old interbase.msg or firebird.msg file.

Limited support for the Services API is now available on Classic server on Linux. Services available from gbak (backup/restore) and gfix (validate database, shutdown/online, etc.) work. Others (gstat, server logs, etc.) were not tested and are probably non-functional.