Tickets :: [#6667] problem with datatree creation scripts

6.0.0-beta1

7/4/25

Summary	problem with datatree creation scripts
Queue	Horde Base
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	liamr (at) umich (dot) edu
Created	05/01/2008 (6273 days ago)
Due
Updated	05/01/2008 (6273 days ago)
Assigned	05/01/2008 (6273 days ago)
Resolved	05/01/2008 (6273 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

05/01/2008 06:46:58 PM	Michael Rubinsky	Comment #5 Assigned to Michael Rubinsky State ⇒ Resolved	Reply to this comment
fixed in HEAD and merged

05/01/2008 05:56:25 PM	Chuck Hagenbuch	Comment #4	Reply to this comment
Yup.

05/01/2008 04:20:49 PM	Michael Rubinsky	Comment #3	Reply to this comment
Actually, this field was dropped as of Horde 3.1.7. I guess we should remove the field in the 3.1->3.2 upgrade sql script for consistency?

05/01/2008 04:17:09 PM	Michael Rubinsky	Comment #2 State ⇒ Feedback	Reply to this comment
That field has been deprecated. What upgrade script are you seeing this in?

05/01/2008 03:49:04 PM	liamr (at) umich (dot) edu	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ problem with datatree creation scripts Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
The scripts in horde/scripts/sql and horde/scripts/upgrades don't create the same horde_datatree table. The table created by the scripts in horde/scripts/sql (create..sql, horde_datatree..sql) lack.. datatree_updated TIMESTAMP, which is included in the upgrade scripts, resulting in a table that is 8 fields in length (rather than 9) This is also a problem with the release candidates. I haven't checked any of the Horde 3.1.x packages.