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.

Sign up for GitHub

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

Jump to bottom

gbak restores invalid views without any warning to the user [CORE2740] #3135

Closed
firebird-automations opened this issue Nov 7, 2009 · 8 comments
Closed

gbak restores invalid views without any warning to the user [CORE2740] #3135

firebird-automations opened this issue Nov 7, 2009 · 8 comments
Labels
affect-version: 1.5.4 affect-version: 1.5.5 affect-version: 1.5.6 affect-version: 2.0.0 affect-version: 2.0.1 affect-version: 2.0.2 affect-version: 2.0.3 affect-version: 2.0.4 affect-version: 2.0.5 affect-version: 2.1.0 affect-version: 2.1.1 affect-version: 2.1.2 affect-version: 2.1.3 affect-version: 2.5 Alpha 1 affect-version: 2.5 Beta 1 affect-version: 2.5 Beta 2 affect-version: 3.0 Initial component: gbak fix-version: 3.0 Alpha 1 priority: major qa: not enough information type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Claudio Valderrama C. (robocop)

Assigned to: Claudio Valderrama C. (robocop)

Attachments:
POORVIEW.Fbk

Gbak needs to calculate the db_key after views have been restored.
The user gets no indication when the maximum recursion for views based on views is reached or when the db_key length calculation leads to an invalid value.

Commits: 749f83a

====== Test Details ======

Broken link to attached file.
@firebird-automations
Copy link
Collaborator Author

Commented by: Claudio Valderrama C. (robocop)

Attachment should be restored and then observe the information in sys tables about the created views.

@firebird-automations
Copy link
Collaborator Author

Modified by: Claudio Valderrama C. (robocop)

Attachment: POORVIEW.Fbk [ 11520 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: Claudio Valderrama C. (robocop)

assignee: Claudio Valderrama C. [ robocop ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Claudio Valderrama C. (robocop)

The user gets an error message but the restore process is not stopped. The user may review the problematic views later.

@firebird-automations
Copy link
Collaborator Author

Modified by: Claudio Valderrama C. (robocop)

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

@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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Not enough information

Test Details: Broken link to attached file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affect-version: 1.5.4 affect-version: 1.5.5 affect-version: 1.5.6 affect-version: 2.0.0 affect-version: 2.0.1 affect-version: 2.0.2 affect-version: 2.0.3 affect-version: 2.0.4 affect-version: 2.0.5 affect-version: 2.1.0 affect-version: 2.1.1 affect-version: 2.1.2 affect-version: 2.1.3 affect-version: 2.5 Alpha 1 affect-version: 2.5 Beta 1 affect-version: 2.5 Beta 2 affect-version: 3.0 Initial component: gbak fix-version: 3.0 Alpha 1 priority: major qa: not enough information type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations