-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
DBAL-1234: Additional slash in dbname when providing settings as URL without scheme #1183
Comments
deeky666
added a commit
to deeky666/dbal
that referenced
this issue
Jan 9, 2016
…river connection parameters - includes extended default driver connection parameter handling - minor refactoring fixes doctrine#1183
Ocramius
pushed a commit
that referenced
this issue
Sep 9, 2016
…river connection parameters - includes extended default driver connection parameter handling - minor refactoring fixes #1183
Ocramius
added a commit
that referenced
this issue
Sep 9, 2016
Handled in #2287 |
1 task
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Jira issue originally created by user KingCrunch:
Hi,
I use https://github.com/realestateconz/MssqlBundle to connect to an MSSQL-database and I'd like to provide the connection parameters as URL. Because
dblib
is not a supported driver I setup thedriverClass
insteadSo the corresponding URL would look like
But now it tries to connect to the database
/databasename
instead ofdatabasename
. I can set an arbitrary scheme here as long as it exists and is supported (and is not SQLite)Now it works, but it's a hack.
It seems, that the issue is here
dbal/lib/Doctrine/DBAL/DriverManager.php
Line 262 in 32b1a4f
As long as there is no scheme the leading slash remains. I'd guess, that it should also take into account, that there might be no driver name, but a concrete
driverClass
instead?
The text was updated successfully, but these errors were encountered: