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

Fix CREATE/DROP DATABASE support on SQL Server #2631

Conversation

deeky666
Copy link
Member

@deeky666 deeky666 commented Feb 5, 2017

It is actually possible to use CREATE DATABASE and DROP DATABASE on SQL Server. The platform did not reflect that. The issue arised when testing SQL Server where the testsuite failed, if the database used by the testsuite didn't exist. With this patch, it works as expected.

@Ocramius
Copy link
Member

Ocramius commented Feb 5, 2017

@deeky666 given that this changes behavior of the platform, wouldn't it better to push it to 2.6 only?

@Ocramius Ocramius self-assigned this Feb 5, 2017
@Ocramius Ocramius modified the milestones: 2.6, 2.5.12 Feb 5, 2017
@Ocramius
Copy link
Member

Ocramius commented Feb 5, 2017

Merging to 2.6 only, but feel free to fight over it with me :-)

@Ocramius Ocramius merged commit 1425f8f into doctrine:master Feb 5, 2017
@deeky666
Copy link
Member Author

deeky666 commented Feb 5, 2017

@Ocramius well in my opinion it is a bug because the the platform does implement all that is necessary (the create/drop SQL) but does not tell the client that this feature is supported. I don't care really, but it will make impossible to test without explicitly creating the database before testing or creating a fresh database via ORM's schema tool.

@Ocramius Ocramius changed the title Fix CREATE/DROP DATABASE support on SQL Server Fix CREATE/DROP DATABASE support on SQL Server Jul 22, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants