Jacopo Cappellato commented on OFBIZ-10953:

Unfortunately it is not desirable to use uomId (i.e. the natural key) to 
populate the dimensionId (i.e. the primary key of the dimension table): in 
fact, based on the update strategy adopted for the dimension table (type 1, 
type 2 etc... as described in "The Datawarehouse Toolkit" book) the 
CurrencyDimension table may contain several rows with the same uomId as this is 
important for properly implementing drill-up and drill-down reports.

> have CurrencyDimension have a dimensionId that is based on the natural key
> --------------------------------------------------------------------------
>                 Key: OFBIZ-10953
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10953
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: bi
>    Affects Versions: Trunk, Release Branch 17.12, Release Branch 18.12
>            Reporter: Pierre Smits
>            Assignee: Pierre Smits
>            Priority: Major
>              Labels: CurrencyDimension, birt, currency, dimension, dwh
>         Attachments: OFBIZ-10953-BI.patch
> Currently the record sequencer (delegator.getNextSeqId) is used to determine 
> the dimensionId for the CurrencyDimension. This is unnecessary as the uomId 
> from the UOM table can be used for currency.
> It also makes it easier to set the foreign-key in fact tables by generating 
> it based on the date provided, than by retrieving the dimensionId based on a 
> retrieval through the getDimensionIdFromNaturalKey service.

This message was sent by Atlassian Jira

Reply via email to