Re: Question related to use of WorkEffortAssoc entity in OFBiz.

[Jacopo Cappellato]

I have to admit that I don't like very much the workEffortParentId field and the way it is used; it would be better if the WorkEffortAssoc entity was used every time you have to specify an association between work effort: in this way you'll have the ability to set the type ofassociation and also validity dates. Sometimes having denormalized fields is useful (to speed up queries and simplify code) but unfortunately the workEffortParentId field is not used only for this and it is used a lot, especially by the manufacturing component, ven when the WorkEffortAssoc would do much more sense.

Jacopo


On Jul 15, 2008, at 11:46 AM, Ashish Vijaywargiya wrote:

My general suggestion would be that of using WorkEffortAssoc as much as possible (especially for new code/features).

Can anybody having good insight on WorkEffort module put some comments to

understand this scenario ?
I am also interested to know about it.

Thanks !!!



wrote:

On Sat, Jun 14, 2008 at 8:46 PM, Rishi Solanki <[EMAIL PROTECTED] >

Hello All,

We have *WorkEffort* Entity in OFBiz in which we maintain a recursive
relation ship using attribute *parentWorkEffortId.*
Here we again have the *WorkEffortAssoc *in which we again relate two
workeffort by using the *workEffortFrom *and* workEffortTo.*
Now my question is like that, if we have a relationship to relate the

need
the
*WorkEffortAssoc *for the same purpose.


Modeling).
**
*
*Thanks and Regards
[Rishi Solanki]*

workEffortId by it self ( i.e by an another workEffortId ), then why we *Or it is for handeling a different scenario in (OFBiz Work Effort Data

--
Ashish Vijaywargiya
Indore, India
http://en.wikipedia.org/wiki/Indore

smime.p7s
Description: S/MIME cryptographic signature