[kronolith] configuring kronolith for use w/ sql

Liam Hoekenga liamr@umich.edu
Tue, 18 Sep 2001 09:18:03 -0400 (EDT)


> $conf['calendar']['driver'] = 'sql';
>
> $conf['calendar']['params'] = array(
>      'phptype'       => 'mysql',
>      'hostspec'      => 'localhost',
>      'protocol'      => 'unix',
>      'username'      => 'hordemgr',
>      'password'      => 'XXXXX',
>      'database'      => 'horde',
>      'port'          => '3306',
>      'table'         => 'kronolith_events'
> );

Ah... I'd tried it originally in Oracle (which also didn't work) - I guess
I forgot to put the database field in why I tried it with mysql.  I've
since gotten it working with mysql, but oracle still is pretty messed up.

If I go into kronolith, using oracle, here's what I get above the
calendar:

object(db_error)(10) { ["error_message_prefix"]=> string(0) ""
["error_prepend"]=> string(0) "" ["error_append"]=> string(0) ""
 ["mode"]=> int(1) ["level"]=> int(1024) ["code"]=> int(-1) ["message"]=>
string(23) "DB Error: unknown error" ["debuginfo"]=> string(0) ""
 ["userinfo"]=> string(314) "SELECT DISTINCT e.event_id FROM
kronolith_events e WHERE e.calendar_id = 'liamr' AND e.event_start >= {ts
 '2001-09-01 00:00:00.000'} AND (e.event_end <= {ts '2001-09-30
23:59:59.999'} OR (e.event_recurEnddate <= {ts '2001-09-30
 23:59:59.999'} AND e.event_recurType != 0)) [nativecode=ORA-00911:
invalid character ]" ["callback"]=> NULL }

here's the oracle setup info:

$conf['calendar']['driver'] = 'sql';
$conf['calendar']['params'] = array();
$conf['calendar']['params']['phptype'] = 'oci8';
$conf['calendar']['params']['hostspec'] = 'mojojojo.world';
$conf['calendar']['params']['username'] = 'hordemgr';
$conf['calendar']['params']['password'] = 'blahblahblah';
$conf['calendar']['params']['table'] = 'KRONOLITH_EVENTS';

I realize that there's no database field here... but this is how the
oracle stuff is setup for horde - and /that/ works.

> Did you set up the tables in MySQL for the kronolith_events per
> $HORDE/kronolith/docs/kronolith.sql:

Yup.

I guess I'm just trying to be too bleeding edge... experimental sql
driver, using a database that only a minority use with this software. ;)

thanks guys
Liam