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

problem restoring long grants [CORE82] #408

Closed
firebird-automations opened this issue May 29, 2006 · 8 comments
Closed

problem restoring long grants [CORE82] #408

firebird-automations opened this issue May 29, 2006 · 8 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: unrz62 (unrz62)

Depends on CORE479

Votes: 1

SFID: 1497029#⁠
Submitted By: unrz62

restoring a db with longer "grant-statements" will fail.

I'm not shure, wether it's the right place to post it
her, but I've tested with fb 1.5.X and 2.0 RC 2 (Linux
32 and 64 bit Classic Server)

Ican't restore the complete db
1.5.3 ends with
gbak: restoring privilege for user SOSWEB
gbak: restoring privilege for user SOSWEB
gbak: restoring privilege for user SOSWEB
gbak: restoring privilege for user PROC_KennungGetId
gbak: ERROR: action cancelled by trigger (0) to
preserve data integrity
gbak: ERROR: could not find table/procedure for GRANT
gbak: Exiting before completion due to errors

2.0 gives an additional hint in BLR:
65 blr_relation, 30,
'F','A','U','S','E','C','_','S','i','c','h','e','r','h','e','i','t','s','b','e','a','u','f','t','r','a','g','t','e','r',
0,

Which is quite a long name.

@firebird-automations
Copy link
Collaborator Author

Commented by: Alice F. Bird (firebirds)

Date: 2006-05-30 07:36
Sender: dimitr
Logged In: YES
user_id=61270

Due to an old bug (inherited from Borland), object names
longer than 27 characters are not supported properly. You
need to rename those objects and then perform backup/restore.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue depends on CORE479 [ CORE479 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Bjoern Reimer (bnreimer)

May be a fast solution, that could be sceduled for one of the next releases, would be one of the follwoing:

1. detect too long grant statements during backup
2. detect too long grant statements during restore and ignore them or print out a warning

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10106 ] => Firebird [ 14291 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

This seems as duplicate of CORE479.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

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

resolution: Duplicate [ 3 ]

@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
Projects
None yet
Development

No branches or pull requests

1 participant