You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2019/04/23 16:50:00 UTC
[jira] [Updated] (OFBIZ-10947) Have DateDimension have a
dimensionId that is based on the natural key
[ https://issues.apache.org/jira/browse/OFBIZ-10947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Smits updated OFBIZ-10947:
---------------------------------
Attachment: OFBIZ-10947-BI.patch
> Have DateDimension have a dimensionId that is based on the natural key
> ----------------------------------------------------------------------
>
> Key: OFBIZ-10947
> URL: https://issues.apache.org/jira/browse/OFBIZ-10947
> Project: OFBiz
> Issue Type: Improvement
> Components: bi
> Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, Release Branch 18.12
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Major
> Labels: birt, dwh
> Attachments: OFBIZ-10947-BI.patch
>
>
> Currently the record sequencer (delegator.getNextSeqId) is used to determine the dimensionId for the DateDimension. This is unnecessary as the date (when correctly formatted) can be used.
> When formatted as 'yyyyMMdd' a dimensionId could be 20190423, which is a correctly 'sequenced' primary key.
> It also makes it easier to set the foreign-key in fact tables by generating it based on the date, than by retrieving the dimensionId based on a retrieval through the getDimensionIdFromNaturalKey service.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)