Firebird Documentation IndexFirebird 1.5.6 Release NotesBugfixes and Additions since Release 1.0 → Release 1.5 and 1.5.1 Bugs Fixed in v.1.5.2
Firebird Home Firebird Home Prev: Release 1.5, 1.5.1 and 1.5.2 Bugs Fixed in v.1.5.3Firebird Documentation IndexUp: Bugfixes and Additions since Release 1.0Next: Release 1.5 Bugs Fixed in v.1.5.1

Release 1.5 and 1.5.1 Bugs Fixed in v.1.5.2

Not registered

fixed by V. Horsun

When a SEGV error (or other asyncronous exception) is thrown from a badly written UDF, the server should log its name. This feature was broken in FB 1.5. Restored in v.1.5.2

Not registered

fixed by V. Horsun, N. Samofatov

In v.1.5.0, exit(3) was called on critical errors on Windows, precluding the use of the JIT debugger to analyse problems in UDF routines. A fix in v.1.5.1 caused the debugger to be called always, introducing a problem with automatic restarts of the server.

V.1.5.2 now calls the debugger only if you set the BugcheckAbort configuration file option to 1. The main goal of the v1.5.2 fix is to avoid Dr.Watson showing its close-or-debug message box.

Not registered

fixed by C. Valderrama

Support for multi-dimensional array fields was broken v1.5.1. Restored in v.1.5.2

Not registered

fixed by V. Horsun, N. Samofatov

Plans for selectable stored procedures containing multiple FOR loops were being reported in reverse order, compared with v.1.5.0. Restored in v.1.5.2

Not registered

fixed by A. Brinkman

In v.1.5.1, a bug in the optimiser caused unnecessary fetches in joined relations when "OR" was used on the base relation. Now fixed

Not registered

fixed by N. Samofatov

There was a problem with deadlock detection when pessimistic locking (WITH LOCK syntax) was used.

  create table test (id integer);
  insert into test values(1);
  insert into test values(2);
  Commit;
          

Transaction 1 (READ COMMITTED, WAIT):

  select * from test
    where id = 1 with lock;
          

Transaction 2 (READ COMMITTED, WAIT):

  select * from test
    where id = 2 with lock;
  select * from test
    where id = 1 with lock;
          

Transaction 1:

  select * from test
    where id = 2 with lock;
        

This set of conditions would result in a permanent deadlock. V.1.5.2 detects and reports such a deadlock as an error.

Not registered

fixed by A. Peshkoff

The server would crash when NULL was passed to EXECUTE STATEMENT ... INTO. For example,

  ...
  VAR = NULL;
  EXECUTE STATEMENT :VAR;
  ...
        

caused the server to die. Now fixed

Not registered

fixed by H. Borrie, D. Yemanov

Documentation for Windows Embedded Server, README.user.embedded in the /doc subdir of the Windows installation, section 2.2 "Database Access" was "corrected" wrongly in v.1.5.1. This section was unclear in v.1.5.0. In v.1.5.1 it was plain wrong. It is now correct.

Prev: Release 1.5, 1.5.1 and 1.5.2 Bugs Fixed in v.1.5.3Firebird Documentation IndexUp: Bugfixes and Additions since Release 1.0Next: Release 1.5 Bugs Fixed in v.1.5.1
Firebird Documentation IndexFirebird 1.5.6 Release NotesBugfixes and Additions since Release 1.0 → Release 1.5 and 1.5.1 Bugs Fixed in v.1.5.2