Dimitry Sibiryakov

Conflict resolution code uses constraint name instead of index name

5

https://github.com/FirebirdSQL/firebird/blame/95442bdfff76d22aafb57b58894047be2a89c6ea/src/jrd/replication/Applier.cpp#L637 If these names are different debug build consistently throw assertion error during execution of test_blob_not_found_in_rw_replica_if_target_row_exists.py.

Non-enforced constraints

24

Partial implementation of #2358 using standard-compliant clause `ALTER CONSTRAINT [NOT] ENFORCED`.

Ability to create an inactive index

1

Implementation of #8090.

`isql -x` always generates the script that creates indices as active even if they are inactive in the database. It makes a database recreated from such script different from source...

BLOB type is not preserved by replication

4

Stream BLOBs become segmented in target database.

Feature Request: support for crypt plugins with only decrypt functionality implemented

3

Currently it is impossible to have a crypt plugin that support only decryption because of the method how database signature is checked. Only working `decrypt()` function should be enough for...

If a crypt plugin returns warnings in status during signature or checksum validation, these warnings are completely ignored instead of being translated into caller's status.

Wrong error code output in EDS

11

If the status vector contains isc_arg_sql_state, EDS code writes SQLSTATE's string address to error message instead of following GDS status like this: ``` Statement failed, SQLSTATE = 42000 Execute statement...

Execution of the test gh_2388_test.py against a debug build of Firebird 6 triggers the assertion `fb_assert(!position || candidate->dependencies)` at innerjoin.cpp:186.