To be sure you understand well my question, here is the point :
<entity entity-name="OrderItem"
package-name="org.ofbiz.order.order"
never-cache="true"
title="Order Item Entity">
...
<field name="productId" type="id"></field>
<field name="productFeatureId" type="id"></field>
...
<relation type="one" fk-name="ORDER_ITEM_PRODUCT"
rel-entity-name="Product">
<key-map field-name="productId"/>
</relation>
For productId you have a relation, but not for productFeatureId. I don't
understand why, or maybe it's an oversight.
Cimballi
On Wed, May 6, 2009 at 10:26 AM, BJ Freeman <[email protected]> wrote:
> firgures if answered #2 it would Answer #1
> :D
>
> Cimballi sent the following on 5/5/2009 7:49 PM:
> > Thanks BJ, here I found the answer for the point 2, missing point 1 ;-)
> >
> > Cimballi
> >
> >
> > On Tue, May 5, 2009 at 8:50 PM, BJ Freeman <[email protected]> wrote:
> >
> >> take a look on page 109 of the Data model book vol 1
> >>
> >> Cimballi sent the following on 5/5/2009 5:20 PM:
> >>> Hi the list,
> >>>
> >>> In the model of the Order application, an "OrderItem" contains a field
> >>> "productFeatureId".
> >>> 1. There is no relation defined for this field, is it normal ?
> >>> 2. It is possible to have a product with several productFeatures, but
> in
> >> an
> >>> orderItem you can specify only one "productFeature". What do you think
> >> about
> >>> having a one to many relation between an orderItem and productFeatures
> ?
> >>>
> >>> Cimballi
> >>>
> >> --
> >> BJ Freeman
> >> http://www.businessesnetwork.com/automation
> >> http://bjfreeman.elance.com
> >>
> >>
> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
> >> Systems Integrator.
> >>
> >>
> >
>
> --
> BJ Freeman
> http://www.businessesnetwork.com/automation
> http://bjfreeman.elance.com
>
> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
> Systems Integrator.
>
>
