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; > > +-------------+---------------------------------------------------------+------------------+----------------+ > > \| 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 \| > >
Attachment
Watch this ticket