Fri, 10 Apr 2026 16:47:25 +0000 https://bugs.horde.org/ticket/7914 MDB2_Schema Error: schema validation error ----> Get the following error from upgrade 1.2.1 to 1.2.2 Type your choice: y Running pre-update scripts... Writing main configuration file Loading database module... Updating database... [ ERROR! ] Reading the existing table structure failed. Error messages: MDB2_Schema Error: schema validation error default value of "alarm_start" is incorrect: "" is not of type "timestamp" Running post-update scripts... Done updating Horde Groupware Webmail Edition. ----> The only way to make the upgrade is deleting the horde_alarms in the MySQL Database. Type your choice: y Running pre-update scripts... Writing main configuration file Loading database module... Updating database... [ OK ] Successfully updated the global tables. [ OK ] Successfully updated the tables for Mail (imp). [ OK ] Successfully updated the tables for Filters (ingo). [ OK ] Successfully updated the tables for Address Book (turba). [ OK ] Successfully updated the tables for Calendar (kronolith). [ OK ] Successfully updated the tables for Tasks (nag). [ OK ] Successfully updated the tables for Notes (mnemo). Done updating tables. Running post-update scripts... Done updating Horde Groupware Webmail Edition. Thu, 29 Jan 2009 19:56:56 +0000 https://bugs.horde.org/ticket/7914#t52106 You got to love MDB2_Schame, eh, MDB2_Schema. Fri, 30 Jan 2009 00:12:15 +0000 https://bugs.horde.org/ticket/7914#t52131 I'm getting this error as well upgrading from 1.2.1 to 1.2.2. Dropping horde_alarms resolved upgrade. Thu, 05 Feb 2009 17:50:57 +0000 https://bugs.horde.org/ticket/7914#t52303 > I'm getting this error as well upgrading from 1.2.1 to 1.2.2. > Dropping horde_alarms resolved upgrade. same error on upgrading from 1.2.2 to 1.2.3 Fri, 01 May 2009 18:45:18 +0000 https://bugs.horde.org/ticket/7914#t53980 Is there an other way to update from 1.2.2 to 1.2.3 ? Mon, 20 Jul 2009 07:54:52 +0000 https://bugs.horde.org/ticket/7914#t54984 I can't reproduce this. Wed, 12 Aug 2009 16:56:59 +0000 https://bugs.horde.org/ticket/7914#t55280 That was not a fresh install from 1.2.2. This 1.2.2 database was created with 1.0.something and got multiple updates until 1.2.2, I hope this history explains the situation. I changed database structure until 1.2.3 update tool got what it expected so updates was successful now. If you cannot reproduce this error it may be helpful to update documentation, so admin has a chance to verify database structure requirements. Thu, 13 Aug 2009 05:05:11 +0000 https://bugs.horde.org/ticket/7914#t55291 The point is, that the MDB2_Schema validator (that we ship) complains about the database schema (that we ship). Since both are always the same, no matter from which version you update, it should either complain for anyone using that Horde version or for no one. Thu, 13 Aug 2009 09:22:22 +0000 https://bugs.horde.org/ticket/7914#t55292 Not reproducible. Wed, 16 Sep 2009 12:40:34 +0000 https://bugs.horde.org/ticket/7914#t55779 FWIW, I just got this exact problem upgrading from 1.2.3 (which comes from older upgrades) into 1.2.4: Running pre-update scripts... Writing main configuration file Loading database module... Updating database... [ ERROR! ] Reading the existing table structure failed. Error messages: MDB2_Schema Error: schema validation error default value of "alarm_start" is incorrect: "" is not of type "timestamp" Running post-update scripts... Done updating Horde Groupware Webmail Edition. I still don't have an indication if the horde_alarms table was updated and even if the rest of the database was correctly updated... or what can I do to prevent this from happening (I can restore my backup, but re-doing the same steps will probably lead to the same error). Wed, 16 Sep 2009 14:48:09 +0000 https://bugs.horde.org/ticket/7914#t55787 Someone who is actually seeing this, has to dig through the code and see where it is coming from. Wed, 16 Sep 2009 14:50:24 +0000 https://bugs.horde.org/ticket/7914#t55788 Or try the following *after* relocating pear with the setup script, but *before* actually doing the upgrade. ./horde/pear/pear -c horde/pear/horde.ini upgrade mdb2_schema-beta ./horde/pear/pear -c horde/pear/horde.ini upgrade mdb2_driver_mysql-beta Replace "mysql" with your database system. Which one do you use anyway? Wed, 16 Sep 2009 14:56:02 +0000 https://bugs.horde.org/ticket/7914#t55789 Well, actually, since this was a production setup which I didn't actually know in what state ended, I rolled everything back to 1.2.3, restored the database, modified the horde_alarms table like this: ALTER TABLE `horde_alarms` CHANGE `alarm_start` `alarm_start` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00' and then successfully upgraded. I'll try to simulate the steps you propose in another directory with a copy of the database but I don't know when I'll have the time (I already took a whole morning with this). What I don't know is how to run the setup script "step by step" so I can relocate pear and then run ./horde/pear/pear -c horde/pear/horde.ini upgrade mdb2_driver_mysql-beta (it is, actually mysql 5.0). Wed, 16 Sep 2009 16:16:19 +0000 https://bugs.horde.org/ticket/7914#t55790 > What I don't know is how to run the setup script "step by step" so I > can relocate pear and then run Just pick the PEAR entry in the menu of setup.php. Wed, 16 Sep 2009 16:21:28 +0000 https://bugs.horde.org/ticket/7914#t55791 same error on upgrade from version 1.2.3 to 1.2.4. Updating database... [ ERROR! ] Reading the existing table structure failed. Error messages: MDB2_Schema Error: schema validation error default value of "alarm_start" is incorrect: "" is not of type "timestamp" => delete horde_alarms and the update is successful without any errors. Mon, 21 Sep 2009 17:14:04 +0000 https://bugs.horde.org/ticket/7914#t55867 Well, that is, unless your users had actually set alarms for a future date and they intend for them to work... if you delete the horde_alarms table, you automatically deleted all your users alarms. You can, however, modify the structure of the table before the upgrade in order that it completes sucessfully: ALTER TABLE `horde_alarms` CHANGE `alarm_start` `alarm_start` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00' This will NOT erase the alarms since it only changes the structure of the table and, actually, it only changes the DEFAULT value (which is used for newly inserted records and doesn't affect existing records). Mon, 21 Sep 2009 17:30:29 +0000 https://bugs.horde.org/ticket/7914#t55868 Changes have been made in CVS for this ticket: Bump versions, even MDB2 and MDB2_Schema because this seems to fix bug #7914. http://cvs.horde.org/diff.php/groupware/config/Attic/pear.txt?rt=horde&r1=1.26.2.8&r2=1.26.2.9&ty=u Wed, 16 Dec 2009 00:06:59 +0000 https://bugs.horde.org/ticket/7914#t57196 This will be fixed with Groupware 1.2.5. Wed, 16 Dec 2009 22:51:44 +0000 https://bugs.horde.org/ticket/7914#t57212 Update to Horde Groupware Webmail Edition 1.2.5 without the error, thank you. Sat, 19 Dec 2009 19:19:39 +0000 https://bugs.horde.org/ticket/7914#t57269