Bug 119828 - Default ancestors denorm not updated when removeChild is called
Summary: Default ancestors denorm not updated when removeChild is called
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: other
Version: nightly
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-02 14:51 UTC by Daniel Berrangé
Modified: 2007-04-18 17:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-02 17:48:02 UTC
Embargoed:

Attachments (Terms of Use)

Description Daniel Berrangé 2004-04-02 14:51:25 UTC 
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):


How reproducible:
Always

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.

Additional info:

This is already causing corruption in production installs, so a script
to fixup the denormalization will be required when resolving this bug.
Comment 1 Daniel Berrangé 2004-04-06 17:03:52 UTC 
Turned out to be rather simple fix in the removeChild(Category) method
- p4 42007.
Comment 2 David Lawrence 2006-07-18 03:59:44 UTC 
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.
Comment 3 Daniel Berrangé 2006-09-02 17:48:02 UTC 
Closing old tickets
Note You need to log in before you can comment on or make changes to this bug.