[Tickets #10902] Re: MySQL syntax wrong in initial install

bugs at horde.org bugs at horde.org
Wed Jan 11 13:23:17 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/10902
------------------------------------------------------------------------------
  Ticket             | 10902
  Updated By         | d.mikhailov at infocommunications.ru
  Summary            | MySQL syntax wrong in initial install
  Queue              | Horde Base
  Version            | 4.0.13
  Type               | Bug
  State              | Unconfirmed
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


d.mikhailov at infocommunications.ru (2012-01-11 13:23) wrote:

Hi everyone,

Fresh install of kronolith-3.0.13 as a part of groupware-4.0.5. Installation
fails:

<QUOTE>
Creating and updating database tables...
====================

Fatal Error:
QUERY FAILED: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near '1
= event_end' at line 1

UPDATE kronolith_events SET event_allday = 1 WHERE event_start +
INTERVAL 'DAY' 1 = event_end

1. Horde_Core_Bundle->migrateDb() /usr/bin/groupware-install:32
2. Horde_Db_Migration_Migrator->up() /usr/share/pear/Horde/Core/Bundle.php:107
3.
Horde_Db_Migration_Migrator->_doMigrate()  
/usr/share/pear/Horde/Db/Migration/Migrator.php:102
4.
Horde_Db_Migration_Base->migrate()  
/usr/share/pear/Horde/Db/Migration/Migrator.php:182
5.
KronolithUpgradeAddAllDay->up()  
/usr/share/pear/Horde/Db/Migration/Base.php:121
6.
KronolithUpgradeAddAllDay->execute()  
/var/www/horde/kronolith/migration/3_kronolith_upgrade_addallday.php:24
7.
Horde_Db_Migration_Base->__call()  
/var/www/horde/kronolith/migration/3_kronolith_upgrade_addallday.php:24
8. call_user_func_array() /usr/share/pear/Horde/Db/Migration/Base.php:86
9. Horde_Db_Adapter_Mysqli->execute()

====================
</QUOTE>

If I comment out line 24 in the
offending 'kronolith/migration/3_kronolith_upgrade_addallday.php',
installation is completed successfully.

Subsequent 'upgrade-install' has no such problem.

Is there an error in the upgrade script?

Best regards,
        Dmitry Mikhailov.


Full install procedure follows. (tried both mysql and mysqli drivers)

# pear install horde/groupware
Did not download optional dependencies: horde/Horde_Test, pear/Date_Holidays,
use --alldeps to download automatically
Did not download optional dependencies: horde/Horde_Test, use --alldeps to
download automatically
Did not download optional dependencies: horde/Horde_Test, use --alldeps to
download automatically
horde/kronolith can optionally use package "horde/Horde_Test" (version >=
1.3.0, version <= 2.0.0, excluded versions: 2.0.0)
horde/kronolith can optionally use package "pear/Date_Holidays" (version >=
0.21.0)
horde/mnemo can optionally use package "horde/Horde_Test" (version >= 1.2.0,
version <= 2.0.0, excluded versions: 2.0.0)
horde/nag can optionally use package "horde/Horde_Test" (version >= 1.2.0,
version <= 2.0.0, excluded versions: 2.0.0)
downloading groupware-4.0.5.tgz ...
Starting to download groupware-4.0.5.tgz (57,815 bytes)
..............done: 57,815 bytes
downloading kronolith-3.0.13.tgz ...
Starting to download kronolith-3.0.13.tgz (2,594,730 bytes)
...done: 2,594,730 bytes
downloading mnemo-3.0.4.tgz ...
Starting to download mnemo-3.0.4.tgz (1,353,512 bytes)
...done: 1,353,512 bytes
downloading nag-3.0.7.tgz ...
Starting to download nag-3.0.7.tgz (1,757,062 bytes)
....done: 1,757,062 bytes
install ok: channel://pear.horde.org/kronolith-3.0.13
install ok: channel://pear.horde.org/mnemo-3.0.4
install ok: channel://pear.horde.org/nag-3.0.7
install ok: channel://pear.horde.org/groupware-4.0.5
[root at infocoms config]# groupware-install

Installing Horde Groupware

Configuring database settings

What database backend should we use?
    (false) [None]
    (mysql) MySQL / PDO
    (mysqli) MySQL (mysqli)
    (pgsql) PostgreSQL
    (sqlite) SQLite

Type your choice []: mysqli

Username to connect to the database as* [] horde
Password to connect with
How should we connect to the database?
    (unix) UNIX Sockets
    (tcp) TCP/IP

Type your choice [unix]: tcp

Database server/host* [] 10.100.10.3

Port the DB is running on, if non-standard [3306]

Database name to use* []
This field is required.

Database name to use* [] infocs_horde

Internally used charset* [utf-8]
Use SSL to connect to the server?
    (1) Yes
    (0) No

Type your choice [0]:

Certification Authority to use for SSL connections []
Split reads to a different server?
    (false) Disabled
    (true) Enabled

Type your choice [false]:

Writing main configuration file... done.

Creating and updating database tables...
====================

Fatal Error:
QUERY FAILED: You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near '1
= event_end' at line 1

UPDATE kronolith_events SET event_allday = 1 WHERE event_start +
INTERVAL 'DAY' 1 = event_end

1. Horde_Core_Bundle->migrateDb() /usr/bin/groupware-install:32
2. Horde_Db_Migration_Migrator->up() /usr/share/pear/Horde/Core/Bundle.php:107
3.
Horde_Db_Migration_Migrator->_doMigrate()  
/usr/share/pear/Horde/Db/Migration/Migrator.php:102
4.
Horde_Db_Migration_Base->migrate()  
/usr/share/pear/Horde/Db/Migration/Migrator.php:182
5.
KronolithUpgradeAddAllDay->up()  
/usr/share/pear/Horde/Db/Migration/Base.php:121
6.
KronolithUpgradeAddAllDay->execute()  
/var/www/horde/kronolith/migration/3_kronolith_upgrade_addallday.php:24
7.
Horde_Db_Migration_Base->__call()  
/var/www/horde/kronolith/migration/3_kronolith_upgrade_addallday.php:24
8. call_user_func_array() /usr/share/pear/Horde/Db/Migration/Base.php:86
9. Horde_Db_Adapter_Mysqli->execute()

====================





More information about the bugs mailing list