[Tickets #7433] Re: scripts/setup.php generates wrong database schema

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7433
------------------------------------------------------------------------------
  Ticket             | 7433
  Updated By         | maxime.charpenne at univ-avignon.fr
  Summary            | scripts/setup.php generates wrong database schema
  Queue              | Horde Groupware
  Version            | 1.2
  Type               | Bug
  State              | No Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


maxime.charpenne at univ-avignon.fr (2008-10-23 13:15) wrote:

> Did you get an error when installing the database through setup.php?
> All fields mentioned in the error message exist in
> scripts/sql/create.xml.

Posting here some additional information. I have the same issue with  
my Horde server (missing fields lock_owner and lock_scope in  
horde_locks table, I didn't check the other tables).

I retry an install from scratch to answer to your question. Apache  
server (2.2.3 on a Debian Etch), MySQL server (5.0.32) and PHP  
(5.2.0). Here is a summary:
  - Download horde-webmail-1.2.tar.gz
  - Extract in DocumentRoot
  - chown -R www-data: .
  - cd script; ./setup.php
      (1) Configure database settings
        answer questions, then during step 'Writing main configuration  
file', this error occurs 10 times:
            Notice: Undefined index:  secret_key in  
/nfswebuapv-test/horde-test.univ-avignon.fr/www/lib/Horde.php on line  
359
      Continuing with (2) Create database or tables
        None error occurs, except a warning because I've manually  
created the database ([  WARN  ] Database horde_test3 already exists,  
skipping.)
  - Finally, I've checked horde_locks :
mysql> desc horde_locks;
+-----------------------+--------------+------+-----+---------+-------+
| Field                 | Type         | Null | Key | Default | Extra |
+-----------------------+--------------+------+-----+---------+-------+
| lock_id               | varchar(36)  | NO   | PRI |         |       |
| lock_principal        | varchar(255) | NO   |     |         |       |
| lock_origin_timestamp | int(11)      | NO   |     | 0       |       |
| lock_update_timestamp | int(11)      | NO   |     | 0       |       |
| lock_expiry_timestamp | int(11)      | NO   |     | 0       |       |
| lock_type             | int(11)      | NO   |     | 0       |       |
+-----------------------+--------------+------+-----+---------+-------+
6 rows in set (0.00 sec)

Still missing two fields.