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

References to non-existent system fields with blr_field are not resolved to NULL [CORE2045] #2481

Closed
firebird-automations opened this issue Aug 19, 2008 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @asfernandes

Since v2.1, engine resolves reference to non-existent system fields to NULL, but it's not working correctly with blr_field (orks only with blr_fid).

A simple backup with procedure parameters don't restore with v2.5 GBAK in v2.1 server.

Commits: 758edeb 31daa65

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Engine bug is fixed, but restore not working due to different security classes names and incompatibility with triggers from ODS 11.1.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

Fix Version: 2.1.2 [ 10270 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

summary: References to non-existent system fields with blr_field are not resolved to NULL - Restore with v2.5 GBAK fail with v2.1 server => References to non-existent system fields with blr_field are not resolved to NULL

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

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