elleffeci wrote:

>
> 1) SQL compatibility: can we be sure that *ALL* SQL queries in our
> application, currently running on FB1.0, will be OK with FB1.5 without
> touching the SQL?

There's some risk that we tightened rules about ambiguous field
references between versions, but that's all.

>
> 2) backward migration: should any problem arise after installing and
> using FB1.5, how can we 'revert' back to v1.0?

Use the V1.0 gbak program and the V1.5 engine and backup the database.
Restore the database using the V1.0 gbak and the V1.0 engine. There's
no guarantee that a V1.0 gbak can read a backup made by a more recent
version of gbak. A new gbak can read backup files created by an older
gbak, and an older gbak can backup the parts of a newer database that it
understands.

> 3) can we hope in a performance gain by migrating to 1.5?

In some cases. Major improvements come with V2. V1.5 was a
deliberately limited release - we wanted to get the C++ code into the
world and tested without building a lot of dependencies so if a problem
was found, applications could revert to 1.0x easily.

>

Regards,


Ann