Bugs fixed Firebird sub-release 2.0.4

<< Sub-release 2.0.5 | Firebird 2.0.7 Release Notes | Sub-release 2.0.3 >>

Bugs fixed

Sub-release 2.0.4

(Unregistered nbackup Bugs) Bugs in nBackup could corrupt databases in some environments. The fixes relate to issues noted in heavy load conditions.

The logic to merge the 'delta' file, which contains the pages which were changed since the nbackup was started, sometimes left the database in a corrupted state.
The logic to merge the 'delta' file sometimes did not mark the database as "unlocked", thus setting the database into an unreconcilable state.
The logic to track which file to write the changed pages to had issues that could result in deadlocks when the backup/merge process was active.

fixed by N. Samofatov

~ ~ ~

(CORE-1775) Security checking during a prepare was performing badly.

fixed by V. Khorsun

~ ~ ~

(CORE-1774) The case-insenstive Spanish language collation ES_ES_CI_AI was exhibiting some problems.

fixed by A. Dos Santos Fernandes

~ ~ ~

(CORE-1746) It was possible (but damaging) to create an expression index while inserts into the table were under way.

fixed by V. Khorsun

~ ~ ~

(CORE-1731) Under some conditions, the engine could "hang" for several minutes, using 100% of CPU resources without any input/output activity.

fixed by V. Khorsun

~ ~ ~

(CORE-1726) Failure could occur during isc_ service_ start().

fixed by A. Peshkoff

~ ~ ~

(CORE-1702) Wrong record number calculation in garbage collector thread.

fixed by V. Khorsun

~ ~ ~

(CORE-1681) An incoming remote packet containing garbage data could crash the server.

fixed by D. Yemanov

~ ~ ~

(CORE-1680) The gsec display command was returning only the first few users from a security database that had more than 50 users installed in it.

fixed by A. Peshkoff

~ ~ ~

(CORE-1679) Output from isc_ service_ query() could contain garbage bytes.

fixed by A. Peshkoff

~ ~ ~

(CORE-1674) The /doc/ sub-directory on Linux installations was being installed without the appropriate access rights.

fixed by A. Peshkoff

~ ~ ~

(CORE-1657) Leaving a read-only, read-committed transaction idle for a long time could cause a memory access violation.

fixed by A. Peshkoff

~ ~ ~

(CORE-1644) Compilation error on GCC 4.1.1

fixed by A. Peshkoff

~ ~ ~

(CORE-1610) A Full server shutdown of Superserver would cause database corruption if it happened while a query modifying data was running.

fixed by D. Yemanov

~ ~ ~

(CORE-1603) A long user name had the potential to cause a buffer overflow.

fixed by A. Peshkoff

~ ~ ~

(CORE-1579) In the 64-bit builds, incorrect memory allocation for BLOB parameters in UDFs was causing the BLOB, if it was NULL and was followed by another parameter, to be overwritten by the value of the next parameter.

fixed by A. Peshkoff

~ ~ ~

(CORE-1572) The error multiple rows in singleton select was not being reported when it occurred in a view.

fixed by A. dos Santos Fernandes

~ ~ ~

(CORE-1549) Subquery-based predicates were are not being evaluated early enough in the join order.

fixed by D. Yemanov

~ ~ ~

(CORE-1533) A JOIN on an ordered derived table was returning the wrong first record.

fixed by D. Yemanov

~ ~ ~

(CORE-1501) SLONG data in dsql_ nod was not being accessed correctly.

fixed by A. Peshkoff

~ ~ ~

(CORE-1500) Data in the internal buffer for EXECUTE STATEMENT was aligned incorrectly.

fixed by A. Peshkoff

~ ~ ~

(CORE-1434) Data used in INTL converters was aligned incorrectly.

fixed by A. Peshkoff

~ ~ ~

(CORE-1484) A memory access violation could occur in fbintl.

fixed by A. Peshkoff

~ ~ ~

(CORE-1481) GFIX could report false errors when using in-memory metadata.

fixed by V. Khorsun

~ ~ ~

(CORE-1476) Forced writes did not work on Linux at all.

fixed by A. Peshkov

~ ~ ~

(CORE-1470) With a multi-file database, the server would crash when a secondary filename exceeded 127 characters.

fixed by C. Valderrama

~ ~ ~

(CORE-1462) A buffer overrun would occur in the optimizer when more than 255 relation references existed in the query, causing the server to crash.

fixed by D. Yemanov

~ ~ ~

(CORE-1460) A client registering its interest in events would crash the server on being connected via the Named Pipes (WNet) protocol.

fixed by D. Yemanov

~ ~ ~

(CORE-1457) The server would crash on attempting to deliver events to a client session that had just disconnected.

fixed by V. Khorsun

~ ~ ~

(CORE-1456) Wrong events delivery was exhibited where there were multiple concurrent XNET connections.

fixed by V. Khorsun

~ ~ ~

(CORE-1455) An unsuccessful user management API call would cause the client library to crash.

fixed by A. Peshkoff

~ ~ ~

(CORE-1452) The client library would crash when attempting to process an event notification received just prior to disconnection.

fixed by D. Yemanov

~ ~ ~

(CORE-1447) A buffer overrun could occur when querying for database info through and isc_ database_info() API call if the database path was very long.

fixed by C. Valderrama

~ ~ ~

(CORE-1434) The client library was misinterpreting the error condition created when isc_attach_database() was called to attach to a read-only database with a read-write transaction: it would return error code 0 instead of 335544727 (net_ write_ err).

fixed by D. Yemanov

~ ~ ~

(CORE-1421) Superserver was unable to shut down immediately upon a shutdown request if a failed login attempt had preceded the request.

fixed by A. Peshkoff

~ ~ ~

(CORE-1419) CURRENT_TIMESTAMP evaluation was being performed incorrectly for selectable procedures.

fixed by D. Yemanov

~ ~ ~

(CORE-1199) Superserver could be brought down by an internal gds software consistency check (CCH_precedence: block marked (212), file: cch.cpp line: 3640).

fixed by V. Khorsun

~ ~ ~

(CORE-1194) An access violation could occur in the client library when a shutdown of Superserver was being handled.

fixed by D. Yemanov

~ ~ ~

(CORE-881) Singleton requirement was not being respected in COMPUTED BY expressions.

fixed by A. dos Santos Fernandes

~ ~ ~

(CORE-100) An old bug in the Windows client library, dating back to v.1.5.3, could cause a memory access violation on disconnecting.

fixed by D. Yemanov

~ ~ ~