-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CLOUDSTACK-10278 idempotent column addition #2449
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
Merged
DaanHoogland
merged 7 commits into
apache:4.11
from
ernjvr:CLOUDSTACK-10278-idempotent-column-add
Mar 28, 2018
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e4b2ca7
CLOUDSTACK-10278 - WIP: need to test this script before create a pull…
ernjvr ab22ad3
CLOUDSTACK-10278 - added more idempotent stored procs and moved all l…
ernjvr 50c2170
CLOUDSTACK-10278 - changed more sql statements to call idempotent sto…
ernjvr 41c34de
CLOUDSTACK-10278 - WIP: need to test this script before create a pull…
ernjvr 7b1c94d
CLOUDSTACK-10278 - added more idempotent stored procs and moved all l…
ernjvr 72acbf4
CLOUDSTACK-10278 - changed more sql statements to call idempotent sto…
ernjvr 33db67c
Merge branch 'CLOUDSTACK-10278-idempotent-column-add' of https://gith…
ernjvr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ernjvr /cc @DaanHoogland @rafaelweingartner - is it possible to refactor these methods out to a Java/sql file, and automatically include them in all sql files so that these procedures may be reused (somehow)? Or, perhaps explore migrating to something else that provides these abstractions, perhaps flywaydb etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would also rather migrate to something like flywaydb too. However, I think it would required quite more work than this one here. What do you think? I have done this analysis before, but I was not having much time, and the discussion died [1]. Maybe we could pick this topic up again?
[1] http://markmail.org/message/2dxtcnqx2euq5tl2
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rafaelweingartner yes, we will have to make sure that everyone creating new scripts to add a new column, drop a foreign key or create/drop indexes, call these stored procedures, to ensure their SQL statements are idempotent.
@rhtyd These 'drop procedure' statements are placed before each 'create procedure' statement only. So when the upgrade script runs, the procedures are created but not dropped after the script completes. Therefore the stored procedures will still exist in the database. So they will be available (reusable) to future versions of schema-nn-nn.sql migration scripts. I think these 'drop/create procedure' statements also need to be added to the setup/db/create-schema.sql script to make them available to new cs installs, including the simulator.