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

Filter out well-known Symfony tables from DBAL schema migrations #1037

Merged
merged 1 commit into from
Oct 23, 2019

Conversation

nicolas-grekas
Copy link
Member

@nicolas-grekas nicolas-grekas commented Oct 21, 2019

This prevents constantly generating DROP TABLE sessions, etc. when generating migrations.

Closes #987

@greg0ire
Copy link
Member

I added a closing comment to your original message, I think it's related :)

@alcaeus
Copy link
Member

alcaeus commented Oct 23, 2019

I like this, as it hopefully solves a lot of problems for people.

Only question I have: would it make sense to require DBAL 2.9? It has been out for almost a year, so I'd hope most people are already running it. We can bump in a separate PR, just thinking that we might as well bump here as this wouldn't work when running anything older than 2.9. WDYT @nicolas-grekas?

@alcaeus alcaeus self-assigned this Oct 23, 2019
@alcaeus alcaeus added this to the 1.12.0 milestone Oct 23, 2019
@alcaeus alcaeus merged commit 2d64753 into doctrine:1.12.x Oct 23, 2019
@alcaeus
Copy link
Member

alcaeus commented Oct 23, 2019

Thanks @nicolas-grekas! We'll bump doctrine/dbal in a separate PR for 2.0 only.

@weaverryan
Copy link
Contributor

Thanks @alcaeus!

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

Successfully merging this pull request may close these issues.

After migration, doctrine deleted session table
4 participants