| 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 (7616 days ago) |
| Due | |
| Updated | 03/22/2005 (7536 days ago) |
| Assigned | 01/02/2005 (7615 days ago) |
| Resolved | 03/22/2005 (7536 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Taken from
I'll take a look at it.
Assigned to
State ⇒ Assigned
db2/odbc; we'd have to make database/protocol optional for all
backends. Jan, any thoughts on this?
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ database access via ODBC error
Queue ⇒ Horde Base
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.