| Summary | problem with datatree creation scripts |
| Queue | Horde Base |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Michael Rubinsky <mrubinsk (at) horde (dot) org> |
| Requester | liamr (at) umich (dot) edu |
| Created | 05/01/2008 (65 days ago) |
| Due | |
| Updated | 05/01/2008 (65 days ago) |
| Assigned | 05/01/2008 (65 days ago) |
| Resolved | 05/01/2008 (65 days ago) |
| Attachments | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Assigned to Michael Rubinsky
I guess we should remove the field in the 3.1->3.2 upgrade sql script
for consistency?
State ⇒ Feedback
What upgrade script are you seeing this in?
Patch ⇒
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ problem with datatree creation scripts
Type ⇒ Bug
Priority ⇒ 1. Low
State ⇒ Unconfirmed
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.