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

Maintain package body after ALTER/RECREATE PACKAGE [CORE4487] #4807

Closed
firebird-issue-importer opened this issue Jul 7, 2014 · 4 comments
Closed

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Jul 7, 2014

Submitted by: Robert (rj1102)

Currently, if I execute an ALTER/RECREATE PACKAGE statement, the package body will be dropped.

I like to request to save the old body source in rdb$packages (e.g. new field rgb$old_package_body_source).

I have then the old body source available when I want to redefine it with RECREATE PACKAGE BODY.

Commits: 409a278 FirebirdSQL/fbt-repository@b33c022

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 31, 2014

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

summary: Save package body after ALTER/RECREATE PACKAGE => Maintain package body after ALTER/RECREATE PACKAGE

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 31, 2014

Commented by: @asfernandes

The source will be maintained and a new column RDB$PACKAGES.RDB$VALID_BODY_FLAG was introduced to indicate the body state.

Invalid body will not be extracted by isql -extract.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jul 31, 2014

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Beta 1 [ 10332 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 28, 2015

Modified by: @pavel-zotov

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

QA Status: Done successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants