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
February 2014 to April 2014
 
April 2014
 
New development:
  • CORE-4386: Report more details for "object in use" errors
Bugfixing:
  • CORE-4388: SELECT WITH LOCK may enter an infinite loop for a single record
  • Fixed ON DISCONNECT triggers (regression)
  • Prevent shutdown/cancellation for system attachments
  • Fixed incorrect generation of attachment IDs causing a hangup during gfix -mode read_only
March 2014
 
New development:
  • Refactored the conjuncts handling code in the optimizer to be simpler and avoid duplication
Bugfixing:
  • CORE-4379: Poor performance of explicit cursors containing correlated subqueries in the select list
  • CORE-4375: Procedure executes infinitely if contains more than 32767 statements inside any BEGIN/END block
  • CORE-4371: Create function/sp which references to non-existent exception: error message is "Error while parsing function's BLR" instead of "exception not defined"
  • CORE-4366: Wrong result of WHERE predicate when it contains NULL IS NOT DISTINCT FROM (select min(NULL) from ...)
  • CORE-4365: Equality predicate distribution does not work for some complex queries
  • CORE-4360: Select from derived table which contains GROUP BY on field with literal value returns wrong result
  • Fixed the optimizer regression reported in fb-devel
February 2014
 
New development:
  • Reworked the hash joins implementation for a better performance (5x-10x boost)
  • Extended the detailed plan output
Bugfixing:
  • CORE-4353: Sorting records are larger than really necessary
  • CORE-4346: v3 GBAK cannot restore backups on pre-v3 server versions
  • CORE-4344: Error "no current record for fetch operation" when table inner join procedure inner join table
  • CORE-4334: Resources (e.g. sort files) owned by trigger may not be released when it's interrupted asynchronously
  • Backported detailed error reporting for conflicts during reading in NORECVER transactions
Dmitry Yemanov
Penza, Russia
February 2014 to April 2014
 
April 2014
 
New development:
  • CORE-4386: Report more details for "object in use" errors
Bugfixing:
  • CORE-4388: SELECT WITH LOCK may enter an infinite loop for a single record
  • Fixed ON DISCONNECT triggers (regression)
  • Prevent shutdown/cancellation for system attachments
  • Fixed incorrect generation of attachment IDs causing a hangup during gfix -mode read_only
March 2014
 
New development:
  • Refactored the conjuncts handling code in the optimizer to be simpler and avoid duplication
Bugfixing:
  • CORE-4379: Poor performance of explicit cursors containing correlated subqueries in the select list
  • CORE-4375: Procedure executes infinitely if contains more than 32767 statements inside any BEGIN/END block
  • CORE-4371: Create function/sp which references to non-existent exception: error message is "Error while parsing function's BLR" instead of "exception not defined"
  • CORE-4366: Wrong result of WHERE predicate when it contains NULL IS NOT DISTINCT FROM (select min(NULL) from ...)
  • CORE-4365: Equality predicate distribution does not work for some complex queries
  • CORE-4360: Select from derived table which contains GROUP BY on field with literal value returns wrong result
  • Fixed the optimizer regression reported in fb-devel
February 2014
 
New development:
  • Reworked the hash joins implementation for a better performance (5x-10x boost)
  • Extended the detailed plan output
Bugfixing:
  • CORE-4353: Sorting records are larger than really necessary
  • CORE-4346: v3 GBAK cannot restore backups on pre-v3 server versions
  • CORE-4344: Error "no current record for fetch operation" when table inner join procedure inner join table
  • CORE-4334: Resources (e.g. sort files) owned by trigger may not be released when it's interrupted asynchronously
  • Backported detailed error reporting for conflicts during reading in NORECVER transactions
Dmitry Yemanov
Penza, Russia