Tickets :: [#1050] database access via ODBC error

6.0.0-alpha12

6/8/25

Summary	database access via ODBC error
Queue	Horde Base
Queue Version	3.0
Type	Bug
State	Resolved
Priority	1. Low
Owners	jan (at) horde (dot) org
Requester	tessarek (at) evermeet (dot) cx
Created	01/01/2005 (7463 days ago)
Due
Updated	03/22/2005 (7383 days ago)
Assigned	01/02/2005 (7462 days ago)
Resolved	03/22/2005 (7383 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/22/2005 05:48:23 PM	Jan Schneider	Comment #4 State ⇒ Resolved	Reply to this comment
This has been implemented with Horde 3.0.4-RC2.

01/21/2005 09:25:22 AM	Jan Schneider	Priority ⇒ 1. Low

01/21/2005 09:25:03 AM	Jan Schneider	Assigned to Jan Schneider Taken from Horde Developers

01/02/2005 07:46:09 PM	Jan Schneider	Comment #3	Reply to this comment
We could probably create a configswitch inside the configsql section. I'll take a look at it.

01/02/2005 07:40:30 PM	Chuck Hagenbuch	Comment #2 Assigned to Horde Developers State ⇒ Assigned	Reply to this comment
I don't think we have an easy way to do either of those now just for db2/odbc; we'd have to make database/protocol optional for all backends. Jan, any thoughts on this?

01/01/2005 06:14:49 PM	tessarek (at) evermeet (dot) cx	Comment #1 State ⇒ Unconfirmed Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ database access via ODBC error Queue ⇒ Horde Base	Reply to this comment
I've set up the Horde framework with IBM's DB2, since DB2 is accessed via the unified ODBC functions within PHP. Horde supports ODBC and therefore this shouldn't be a problem. First I've got an error but then I was able to solve the problem by editing the conf.php. The ['protocol'] and ['database'] parameters have to be set to an empty string. Then Horde works perfectly with DB2 via ODBC. Unfortunately the protocol and the database name are required fields in the Horde-Administration-Configuration web interface. I just wanted to tell you that Horde works with IBM DB2, but that you will have to edit the conf.php file manually. If you are interested, I can send you the create tables script for DB2. To solve the required field problem in the administration interface there are several possibilities: 1) Create a new database backend item called DB2, where protocol and database are not required fields. 2) Change the field requirements for ODBC.