Validating conflict avoiding and volatile

Posted by / 17-Apr-2019 01:23

The v.2.0 release cycle of Firebird brought a large collection of long-awaited enhancements under the hood that significantly improved performance, security and support for international languages.Several annoying limitations, along with a huge pile of old bugs inherited from the legacy code, have gone.During Firebird 2.1 development it was discovered that Forced Writes had never worked on Linux, in either the Inter Base or the Firebird era.That was fixed in V.2.1 and backported to this sub-release.

It incorporates a number of bug fixes that did not make it into the v.2.0.6 sub-release in June 2010 or have been backported from subsequent 2.1.x and 2.5.x releases.Calculation of index statistics has been revamped to improve the choices the optimizer has available, especially for complex outer join distributions and DISTINCT queries.Many new additions have been made to the SQL language, including support for derived tables (SELECT ... FROM), PSQL blocks in dynamic SQL through the new EXECUTE BLOCK syntax and some handy new extensions in PSQL itself.An attempt to prepare the DDL statement would result in an “ The on-disk structure (ODS) of the databases created under Firebird has changed.Although Firebird 2.0 will connect to databases having older ODS versions, most of the new features will not be available to them.

validating conflict avoiding and volatile-76validating conflict avoiding and volatile-46validating conflict avoiding and volatile-58

It will become publicly available in a subsequent v.2.x release.

One thought on “validating conflict avoiding and volatile”