Otis wrote:
LG wrote:
Hello,
in our team we are using LLBLGen (version 5.6 (5.6.2) RTM) for generating Entity classes code. How could we use multiple source databases for DB reverse engineering to be able to keep one's work isolated from our main code branch (ie. main DB, and multiple dev DBs)?
Your entity models are also separate from each other or do you use a single entity model in the end? Do you share catalogs with each other for readonly purposes? Could you give a bit more info how it looks now? E.g. user A works on database A, user B works on database B, and A and B's models are not connected or if they are connected how do you do that now?
Some teams work with separate databases per developer, and export changes which are merged into the central database which is then used to generate code for further development. As entities are the same this isn't a problem.
Hi,
our project is quite big (>50 entities), and developers may work on the same entity in the same time, but on different git branches (for example when there are 2 or more tasks related to the same part of code). So, developer A works on his DEV_A_DB, developer B, works on his DEV_B_DB, and their work may be related to the same entity, or there could be relationship between entities. The problem is - depending on who commit changes first, and in which moment of time other developers pull mentioned changes they could create strange conflicts when integrating their changes to, let say, DEV_MAIN_DB (for example Dev C has only code changes from Dev A but not B, but he has database with A+B changes). How could we integrate their changes into DEV_MAIN_DB without breakage in easy way?
