Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugcheck when PK\UK\FK constraint check read record already marked as damaged [CORE6150] #6399

Closed
firebird-issue-importer opened this issue Sep 30, 2019 · 4 comments

Comments

@firebird-issue-importer

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

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 30, 2019

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 30, 2019

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0.5 [ 10885 ]

Fix Version: 4.0 Beta 2 [ 10888 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 30, 2019

Commented by: Jesus Angel Garcia Zarco (cointec)

Will it be solved in 2.5 version?

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 30, 2019

Commented by: @hvlad

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment