Chris,
Can I say that I can safely ignore ProductCategory.primaryParentCategoryId in my logics, but still
dutifully populate it (ie, copy value from ProductCategoryRollup.parentProductCategoryId)?
> I'd be happy to answer your "Do I use CategoryWorker.java" question if you
> could answer..."For what?"
Trying to do a "deep search" for all descendants of a ProductCategory, the
entire hierarchy.
Yeah, I know I shouldn't have said "for retrieving all the child categories".
Sorry. :P
Jonathon
Chris Howe wrote:
There may be a service, but depending on what data you're trying to
retrieve it may be unnecessary to use. Is doing a search against the
ProductCategoryRollup entity insufficient?
ProductCategory.primaryParentCategoryId is a
denormalized/non-normalized field. It's denormalized because the same
entry should exist in ProductCategoryRollup. It's non-normalized
because ProductCategoryRollup doesn't have a rollupTypeId field to
specify an importance that the "primary" part of the description
depicts. Being non-normalized here is rather trivial.
I'd be happy to answer your "Do I use CategoryWorker.java" question if
you could answer..."For what?"
--- Jonathon -- Improov <[EMAIL PROTECTED]> wrote:
Is there a service for retrieving all the child categories belonging
to a parent category? Is the
related entity ProductCategoryRollup? This entity seems to allow a
child category to have more
than 1 parent category.
What about field ProductCategory.primaryParentCategoryId?
I see services "createProductCategory" (and update) used to create
the necessary
ProductCategoryRollup record, but not anymore. Same for service
"updateProduct".
Do I use the CategoryWorker.java?
Jonathon
