Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-11414 Improve the BI component
  3. OFBIZ-10947

Have DateDimension have a dimensionId that is based on the natural key

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Patch Available
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Release Branch 16.11, Release Branch 18.12, Release Branch 17.12, Trunk
    • Fix Version/s: None
    • Component/s: bi

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pierresmits Pierre Smits
                Reporter:
                pierresmits Pierre Smits
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: