Does each team member need to link to Git repo branch when using shared model

bitshift2bitshift2 Posts: 11 New member
edited November 13, 2018 9:13PM in SQL Source Control
Lets say a team of 3 are using the "shared" model, linking a database on a development server.  If I read the docs correctly, only 1 person needs to do this?  Then, if the others have sql source control installed on their workstation, then wont the Db icons be updated to indicate they are setup - or does each member need to go through the "link" step, using the same Git repo path?


update:  I think I know why - I chose "working folder", instead of mapping to a git repo
https://documentation.red-gate.com/soc6/linking-to-source-control/other-source-control-systems/link-to-a-working-folder
However, the question still stands - does each team member need to do the "link" step? 
Tagged:
· Share on Twitter

Best Answer

  • David AtkinsonDavid Atkinson Posts: 1,462 Rose Gold 2
    Answer ✓
    All users need to do this as the information that "links" the dev DB (shared or otherwise) to the VCS repo or working folder is per-user. This is because not all users might choose to use the same working folder path on their disk. There is an argument that when using the native VCS integration the tool should be able to "auto link", but this functionality doesn't exist yet.
    David Atkinson
    Product Manager
    Redgate Software
    · Share on Twitter

Answers

  • bitshift2bitshift2 Posts: 11 New member
    Yes, I Git it now (haha).  The "link" step is really just setting the Db to point to a local Git repo.  Since each team member will clone the repo to a path local to them, then they will need to do the link step also.  Thanks.
    · Share on Twitter
  • Mike UMike U Posts: 316 Gold 1
    That's also why the shared model isn't really compatible with Git, because each developer has their own local repository which can change independently of any central remote you might have configured.
    Development Lead
    Redgate Software
    · Share on Twitter
  • LeeRobinsonLeeRobinson Posts: 19 Bronze 2
    edited July 21, 2022 7:13PM
    Mike U's comment about the shared model not being compatible with Git does not make any sense to me.  Even in dedicated mode, each developer has their own local repository which can change independently of any central remote.  I see no difference as far as repositories go.  Regarding actual history of changes, the Source Control is independent of the database.
    · Share on Twitter
Sign In or Register to comment.