Forum Stats

  • 3,752,505 Users
  • 2,250,511 Discussions
  • 7,867,861 Comments

Discussions

Adding/Mixing Data Modeler with Existing Git Project

_Dylan_
_Dylan_ Member Posts: 587 Bronze Badge

Is there any guidance for/against mixing a new Data Model with an existing Git project/repo? I have an existing git project that contains DDLs for different DB Objects, scripts used for deployments, xmls for related ETL Tools, etc. I would like to add a Data Model to the project, and going forward include model changes as part of feature branches that introduce those changes...if feasible. Maybe not so much if issuing git commands outside of the tool (like rebasing a long running feature branch) are likely to mess things up.

Best Answer

  • Philip Stoyanov-Oracle
    Philip Stoyanov-Oracle Member Posts: 3,343 Employee
    edited Aug 11, 2020 9:34AM Accepted Answer
    Is there any guidance for/against mixing a new Data Model with an existing Git project/repo?

    It doesn't matter if it's one design or several designs in one repository. Standalone version of DM can properly filter changes at design level if your designs and system data types directory are layout properly in file system (repository) - see following for details

    It's up to you to have additional content outside the directories for DM artifacts.

    Philip

Answers

  • Philip Stoyanov-Oracle
    Philip Stoyanov-Oracle Member Posts: 3,343 Employee
    edited Aug 11, 2020 9:34AM Accepted Answer
    Is there any guidance for/against mixing a new Data Model with an existing Git project/repo?

    It doesn't matter if it's one design or several designs in one repository. Standalone version of DM can properly filter changes at design level if your designs and system data types directory are layout properly in file system (repository) - see following for details

    It's up to you to have additional content outside the directories for DM artifacts.

    Philip