Fri, 10 Apr 2026 11:02:31 +0000 https://bugs.horde.org/ticket/4732 New, faster datatree history migration script This is a new, faster script to migrate the history information from the old DB schema to the new, seprate-table schema. This version is 3000+ times faster for me, which makes me think I've missed some error checks or cleanup or something, but AFAICT it does the same thing as the current script. Here's my mailing original list post: http://article.gmane.org/gmane.comp.horde.user/16366 Josh Tue, 05 Dec 2006 14:33:43 +0000 https://bugs.horde.org/ticket/4732#t27016 One thing I've noticed with some more testing is that I have some datatree elements that don't have any attributes. These rows don't get deleted from the old history database, and I'm not sure if they are supposed to or not. Here is a snip of these rows: mysql> SELECT c.datatree_id, c.datatree_name, c.datatree_parents, c.datatree_order FROM horde_datatree c WHERE c.group_uid = 'horde.history' order by datatree_id; +-------------+---------------------------------------------------------+------------------+----------------+ | datatree_id | datatree_name | datatree_parents | datatree_order | +-------------+---------------------------------------------------------+------------------+----------------+ | 4 | nag | | NULL | | 13 | imp | | NULL | | 17 | turba | | NULL | | 18 | localsql | :17 | NULL | | 342 | horde | | NULL | | 343 | group | :342 | NULL | | 1285 | kronolith | | NULL | | 3401 | user@foo.com | :17 | NULL | Tue, 05 Dec 2006 14:46:16 +0000 https://bugs.horde.org/ticket/4732#t27017 > One thing I've noticed with some more testing is that I have some > datatree elements that don't have any attributes. These rows don't > get deleted from the old history database, and I'm not sure if they > are supposed to or not. Here is a snip of these rows: > > mysql> SELECT c.datatree_id, c.datatree_name, c.datatree_parents, > c.datatree_order FROM horde_datatree c WHERE c.group_uid = > 'horde.history' order by datatree_id; Yes, those are probably parent entries. I haven't had a chance to look yet to see why your script isn't deleting them, but you should be able to kill everything with a group_uid of horde.history. Then you can use this snippet to find any "orphaned" datatree_ids that should be purged from horde_datatree_attributes: SELECT DISTINCT da.datatree_id FROM horde_datatree_attributes da LEFT JOIN horde_datatree d ON da.datatree_id = d.datatree_id WHERE d.datatree_id IS NULL Tue, 05 Dec 2006 19:08:26 +0000 https://bugs.horde.org/ticket/4732#t27029 > Yes, those are probably parent entries. I haven't had a chance to > look yet to see why your script isn't deleting them, but you should > be able to kill everything with a group_uid of horde.history. Then > you can use this snippet to find any "orphaned" datatree_ids that > should be purged from horde_datatree_attributes: The lines are not deleted because the delete statements are within the attribute loop, and since there are no attributes it never enters that loop. Moving the delete lines out of that loop (down three lines) should take care of it. They should probably be outside the loop anyway since they have nothing to do with the data tree object's attributes, only the object itself, oops! Josh Tue, 05 Dec 2006 21:18:57 +0000 https://bugs.horde.org/ticket/4732#t27030 Committed, thanks. Sat, 09 Dec 2006 02:37:19 +0000 https://bugs.horde.org/ticket/4732#t27236