Tickets :: [#1596] mysql database dsn ~ horde not using port from config

Summary	mysql database dsn ~ horde not using port from config
Queue	Horde Framework Packages
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	andrew.nimmo+horde.org (at) email (dot) sh
Created	03/21/2005 (7383 days ago)
Due
Updated	03/21/2005 (7383 days ago)
Assigned
Resolved	03/21/2005 (7383 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/21/2005 06:41:27 PM	Jan Schneider	Comment #3 State ⇒ Not A Bug	Reply to this comment
The parameters are passed as-is to PEAR's DB package. If it doesn't use this parameters, it's DB's fault. Try upgrading to the latest DB version, and report a bug on pear.php.net if that doesn't help.

03/21/2005 05:48:10 PM	andrew (dot) nimmo+horde (dot) org (at) email (dot) sh	Comment #2	Reply to this comment
horde 3.0.3 (release)

03/21/2005 05:43:39 PM	andrew (dot) nimmo+horde (dot) org (at) email (dot) sh	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ mysql database dsn ~ horde not using port from config Queue ⇒ Horde Framework Packages	Reply to this comment
a recent mysql database move highlighted an issue with the database port parameter. i have a mysql instance running on port 3307 (it's actually the endpoint of an stunnel). horde ignores the port specification, for example: - horde/conf.php $conf['sessionhandler']['params']['port'] = 3307; $conf['sessionhandler']['params']['hostspec'] = '192.168.0.130'; the obvious workaround is to specify the port parameter directly in the hostspec: $conf['sessionhandler']['params']['hostspec'] = '192.168.0.130:3307'; andrew