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

RevEng: Ignore __MigrationHistory table #1929

Closed
rowanmiller opened this issue Mar 27, 2015 · 3 comments
Closed

RevEng: Ignore __MigrationHistory table #1929

rowanmiller opened this issue Mar 27, 2015 · 3 comments
Assignees
@lajones
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone
1.0.0

Comments

@rowanmiller
Copy link
Contributor

If this table is in the database we should exclude it from reverse engineer
@lajones
Copy link
Contributor

lajones commented Mar 28, 2015

Is it always called __MigrationHistory or is it configurable?

@rowanmiller
Copy link
Contributor Author

I think it's fine just to match on that name... that's what we did in the Power Tools. Obviously for the UI workflow folks can choose if they want that table included or not.

@rowanmiller rowanmiller added this to the 7.0.0 milestone Mar 30, 2015
@lajones
Copy link
Contributor

lajones commented Apr 29, 2015

Fixed by #2089

@lajones lajones closed this as completed Apr 29, 2015
@rowanmiller rowanmiller modified the milestones: 7.0.0, 7.0.0-beta6 Jul 15, 2015
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta6, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lajones lajones

Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
3 participants
@ajcvickers @lajones @rowanmiller