Skip to content

Fix: getMigrationDbMap method incorrectly uses the global migration set#236

Closed
charithe wants to merge 1 commit intorubenv:masterfrom
cerbos:fix-get-db-map
Closed

Fix: getMigrationDbMap method incorrectly uses the global migration set#236
charithe wants to merge 1 commit intorubenv:masterfrom
cerbos:fix-get-db-map

Conversation

@charithe
Copy link
Copy Markdown

Setting DisableTableCreate on a MigrationSet has no effect because the getMigrationDbMap method on MigrationSet uses the global migSet instead of the instance variable.

Signed-off-by: Charith Ellawala charith.ellawala@gmail.com

The `getMigrationDbMap` method on `MigrationSet` uses the global
`migSet` to check whether table creation is disabled. It should be
checking the instance variable instead.

Signed-off-by: Charith Ellawala <charith.ellawala@gmail.com>
@peterldowns
Copy link
Copy Markdown
Contributor

@charithe I just noticed that you had written this PR, I also wrote a PR to fix the same problem #242 . Hopefully one or both of these can get merged.

@rubenv
Copy link
Copy Markdown
Owner

rubenv commented Jun 6, 2023

#242 fixed this

@rubenv rubenv closed this Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants