軟體下載 Firebird 2.5.5 (64-bit)

• 1

  版本確認

• 2

  檔案準備中

• 3

  檔案下載

What's new in this version:

Bug fixes:
- IMPROVEMENT: Improve validation and fixup of lost data pages
- Casting DATE to string would break in Dialect 1 in the presence a domain with a CHECK constraint
- A view or subquery with UNION would not use a computed index
- IIF function was preventing the condition from being pushed into the union for better optimization
- Predicate IS [NOT] DISTINCT FROM was not being pushed into unions/aggregates, resulting in sub-optimal plans
- ALTER DOMAIN ... TO would allows the to be specified in the same pattern as domains generated by the system, i.e., matching to 'RDB$[[:DIGIT:]]*'
- MERGE / HASH JOINs would produce incorrect results when VARCHAR join keys differed only by trailing spaces
- The server could hang on simultaneous connection to the Services API and a database
- An invalid internal BLR filter conversion was detected
- Index corruption could occur while inserting data into a long-key-indexed field
- Preparing a query with a PLAN clause in a CTE could crash the server
- A memory leak was detected in Superserver
- MERGE JOIN could be used for expressions involving RDB$DB_KEY
- MERGE JOIN was not being used for more than two streams if they were joined via USING/NATURAL clauses
- Timestamps could be cast to strings that were beyond the valid range for VARCHAR
- The full text of the problem value was not being returned in the message “Problematic key value (attempting to insert duplicate in PK/UK)” when the length of the offending key was 127 characters or longer
- ON CONNECT triggers would sometimes fail to execute
- A request synchronization error could occur while building an expression index
- Bugcheck 167 (invalid SEND request) could occur while working with a GTT from several attachments, using EXECUTE STATEMENT ... ON EXTERNAL and different roles
- EXECUTE STATEMENT using BLOB parameters could result in an “Invalid BLOB ID” error
- The error “invalid BLOB ID” could occur when retrieving MON$STATEMENTS.MON$SQL_TEXT using EXECUTE STATEMENT against an EXTERNAL DATA SOURCE and the argument db_connect was not specified
- Deadlock could occur during attachment
- The server could hang while chasing dead record versions.
- CREATE TABLE would throw an error if a column was being defined with the character set DOS775
- COUNT(DISTINCT ...) was too slow

Windows-Specific:
- Online validation on Windows would fail if the dbname argument contained forward slash ('/') and a concurrent attachment existed that also used '/'
- Embedded server on Windows could hang due to a synchronization problem involving artifact child processes that were not detectable by Firebird
- The Control Panel applet Firebird2Control.cpl would crash in Windows 8