Tickets :: Comment on [#4732] New, faster datatree history migration script

* Your Email Address
* Spam protection	Enter the letters below: .__ . ._..__ . . [__)\| \| [__)\| \| \| \|____\|_[__)\|/\\|
Comment	>> 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
Attachment
Watch this ticket