[#CORE-6150] Bugcheck when PK\UK\FK constraint check read record already marked as damaged

Firebird Core

Bugcheck when PK\UK\FK constraint check read record already marked as damaged

Created: 30/Sep/19 11:32 AM Updated: 30/Sep/19 05:44 PM

Component/s:

Engine

Affects Version/s:

2.5.0, 2.5.1, 2.5.2, 2.5.2 Update 1, 2.5.3, 2.1.7, 2.5.3 Update 1, 2.5.4, 2.5.5, 4.0 Initial, 3.0.0, 2.5.6, 3.0.1, 2.5.7, 3.0.2, 4.0 Alpha 1, 2.5.8, 3.0.3, 3.0.4, 4.0 Beta 1, 2.5.9

Fix Version/s:

3.0.5, 4.0 Beta 2

QA Status:

No test

Description

« Hide

I have customer (private) database with few records marked as damaged (by gfix -mend).
When new record inserted refers to the damaged record, engine tries to read damaged record and fails with a bugcheck error.
Correct behaviout is to skip damaged record as it is already done by usual SELECT statement processing.

All

Comments

Change History

Subversion Commits

Sort Order:

[ Permalink | « Hide ]

Jesus Angel Garcia Zarco added a comment - 30/Sep/19 05:30 PM

Will it be solved in 2.5 version?

[ Permalink | « Hide ]

Vlad Khorsun added a comment - 30/Sep/19 05:44 PM

The patch is commited into B2_5_Release branch, but we have no plan to release 2.5.10 so far.