Red Hat Bugzilla – Bug 119828
Default ancestors denorm not updated when removeChild is called
Last modified: 2007-04-18 13:05:21 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create two categories
2. Make one a child of the other
3. Remove the child using 'parent.removeChild(child)'
Actual Results: The default ancestors field in the DB for the
ex-child category still refers to the original path. ie /0001/0002/
instead of /0002/.
Expected Results: The denormalization is updated whenever the
category mappings change.
This is already causing corruption in production installs, so a script
to fixup the denormalization will be required when resolving this bug.
Turned out to be rather simple fix in the removeChild(Category) method
- p4 42007.
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.
Closing old tickets