Join Firebird!

Join Firebird Foundation to support Firebird SQL development and receive multiple bonuses

Follow Us

Select your media preference

Newsletter

Subscribe to Firebird’s Newsletter to receive the latest news

Developer's Report: Firebird Core Development & Coordination
May to August 2015
 
August 2015
 
New development:
  • Core support for 32KB page size
Bugfixing:
  • CORE-4909: MERGE / HASH JOINs produce incorrect results when VARCHAR join keys differ only by trailing spaces
  • CORE-4497: Wrong handling in FOR-cursor when NOT EXISTS( select from ) statement is used to check results obtained from SP
  • Fixed the hash function for in-process compatible locks
July 2015
 
Bugfixing:
  • CORE-4872: v3 fbclient cannot work with servers older than v2.5 via the remote protocol
  • CORE-4867: Server crash when preparing a query with PLAN clause at some CTE
  • CORE-4710: invalid request BLR at offset 361 context already in use (BLR error)
  • CORE-4107: wrong resultset (subquery + derived table + union)
  • Fixed hostless INET/WNET connection strings on Linux
  • Fixed the SHOW SEQU output on 64-bit Linux
June 2015
 
Bugfixing:
  • CORE-4839: SHOW GRANTS does not display info about exceptions which were granted to user
  • CORE-4618: Rollback doesn`t undo changes when MERGE statement updates the same target rows multiple times and PLAN MERGE is used
  • CORE-4561: BUGCHECK(183) when use cursor with "order by ID+0" and "for update with lock"
  • CORE-4369: BUGCHECK(177) for MERGE with multiple matches
  • Restored the pre-v3 prefetch performance
May 2015
 
Bugfixing:
  • CORE-4822: MERGE JOIN cannot be used for DBKEY based expressions
  • CORE-4809: HASH/MERGE JOIN is not used for more than two streams if they are joined via USING/NATURAL clauses and join is based on DBKEY concatenations
  • CORE-4806: Regression: generators can be seen/modified by unprivileged users
  • CORE-4798: Regression: MIN/MAX with a join ignores possible index navigation
  • CORE-4786: Problematic key value (when attempt to insert duplicate in PK/UK) is not shown where length of key >= 127 characters
  • CORE-214: Count ( DISTINCT ... ) is too slow
  • Fixed bad handling of zero-length segments coming from internally filtered blobs
 
Dmitry Yemanov
Penza, Russia
 
May to August 2015
 
August 2015
 
New development:
  • Core support for 32KB page size
Bugfixing:
  • CORE-4909: MERGE / HASH JOINs produce incorrect results when VARCHAR join keys differ only by trailing spaces
  • CORE-4497: Wrong handling in FOR-cursor when NOT EXISTS( select from ) statement is used to check results obtained from SP
  • Fixed the hash function for in-process compatible locks
July 2015
 
Bugfixing:
  • CORE-4872: v3 fbclient cannot work with servers older than v2.5 via the remote protocol
  • CORE-4867: Server crash when preparing a query with PLAN clause at some CTE
  • CORE-4710: invalid request BLR at offset 361 context already in use (BLR error)
  • CORE-4107: wrong resultset (subquery + derived table + union)
  • Fixed hostless INET/WNET connection strings on Linux
  • Fixed the SHOW SEQU output on 64-bit Linux
June 2015
 
Bugfixing:
  • CORE-4839: SHOW GRANTS does not display info about exceptions which were granted to user
  • CORE-4618: Rollback doesn`t undo changes when MERGE statement updates the same target rows multiple times and PLAN MERGE is used
  • CORE-4561: BUGCHECK(183) when use cursor with "order by ID+0" and "for update with lock"
  • CORE-4369: BUGCHECK(177) for MERGE with multiple matches
  • Restored the pre-v3 prefetch performance
May 2015
 
Bugfixing:
  • CORE-4822: MERGE JOIN cannot be used for DBKEY based expressions
  • CORE-4809: HASH/MERGE JOIN is not used for more than two streams if they are joined via USING/NATURAL clauses and join is based on DBKEY concatenations
  • CORE-4806: Regression: generators can be seen/modified by unprivileged users
  • CORE-4798: Regression: MIN/MAX with a join ignores possible index navigation
  • CORE-4786: Problematic key value (when attempt to insert duplicate in PK/UK) is not shown where length of key >= 127 characters
  • CORE-214: Count ( DISTINCT ... ) is too slow
  • Fixed bad handling of zero-length segments coming from internally filtered blobs
 
Dmitry Yemanov
Penza, Russia