Closed doctrinebot closed 8 years ago
Comment created by @doctrinebot:
A related Github Pull-Request [GH-620] was closed: https://github.com/doctrine/dbal/pull/620
Comment created by @ocramius:
Merged: https://github.com/doctrine/dbal/commit/247bd099b8f74eed3d7bdb42a5e0bb1af1925dce
Issue was closed with resolution "Fixed"
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.
Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of Slashbunny:
Url: https://github.com/doctrine/dbal/pull/620
Message:
It looks like this was a simple typo.
References: SQLA16 - http://dcx.sybase.com/index.html#sa160/en/dbadmin/serverport-network-conparm.html SQLA12 - http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.11.0.1/dbadmin_en11/serverport-network-conparm.html
It probably wasn't noticed immediately due to the fact SQL Anywhere drivers cache database server address information in a file on disk (sasrv.ini). Once the cache is populated with the database name, it's possible to connect successfully even if the port you were specifying in your code was incorrect (like 2683).
http://dcx.sybase.com/1201/en/dbadmin/servernamecaching.html