Optimal way to generate entities for multi developer team

Posts   
 
    
Damodar
User
Posts: 23
Joined: 30-May-2013
# Posted on: 30-May-2013 18:35:43   

Hi,

We have around 10 developers in our team and we use peoplesoft as the databases and the entity would be generated as C# classes. There are many occasions when there are multiple views created/updated in a day and when a particular developer refeshes the relational data model from database, all the changes come in, now the project explorer has all those additional changes apart from my changes, but i do not want to be checking in others changes. I tried to select just my view and generate the entities but it breaks the build. Please suggest a way so that we can only select our view/table and generate the entity only for that.

Thanks and regards, Damodar

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 30-May-2013 19:45:32   

In your case, it seems developers modify the schema of a common database without checking in their code modifications.

Typically developer changes to the database should be committed with the corresponding code. So the best practice is that each team has their own database version, and they only submit changes to the main database when checking in the corresponding code.

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 31-May-2013 08:27:13   

I also think that each sub-team should have their own test DB. A good approach for me is to use mercurial to upload the original code-base, this code base also includes the DB schema script. Each sub-team then forks the code-base to create a code branch, they update their own DB and update the create script (either with a full script or alters). If Team A wants the changes made by Team B, then they merge the commits into the main branch... something like that. That way, also makes it possible to detect who sub-team made what change, etc.

David Elizondo | LLBLGen Support Team