Bugcheck when PK\UK\FK constraint check read record already marked as damaged [CORE6150] #6399
Labels
affect-version: 2.1.7
affect-version: 2.5.0
affect-version: 2.5.1
affect-version: 2.5.2 Update 1
affect-version: 2.5.2
affect-version: 2.5.3 Update 1
affect-version: 2.5.3
affect-version: 2.5.4
affect-version: 2.5.5
affect-version: 2.5.6
affect-version: 2.5.7
affect-version: 2.5.8
affect-version: 2.5.9
affect-version: 3.0.0
affect-version: 3.0.1
affect-version: 3.0.2
affect-version: 3.0.3
affect-version: 3.0.4
affect-version: 4.0 Alpha 1
affect-version: 4.0 Beta 1
affect-version: 4.0 Initial
component: engine
fix-version: 3.0.5
fix-version: 4.0 Beta 2
priority: major
type: bug
Submitted by: @hvlad
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.
Commits: 7f944f5 ecbb17b 53c0bd7
The text was updated successfully, but these errors were encountered: