Adding new tables to the model without doing full db refresh

Posts   
 
    
AlbertK
User
Posts: 44
Joined: 23-Dec-2009
# Posted on: 07-Jul-2011 18:31:32   

I work in the environment with very large databases (in terms of number of objects) - thousands of tables. I like to keep the LLBLGen project file small, so I only pick the tables that I need to work with. Then, I find myself needing to add a new table to the model so I can reverse engineer it. I really like the fact that 3.1 designer saves project in XML format, so it's easy for me to diff project files to see what changed.

What I find bothersome is that I have to do a full refresh of all databases in the project to add a new table from a single database. Moreover, the full refresh tends to have side effects on existing entities (like dropping type converters). Is there a way to simply add new objects to the model without refreshing existing entities? If not, I think it would be a good enhancement. Thank you.

MTrinder
User
Posts: 1461
Joined: 08-Oct-2008
# Posted on: 07-Jul-2011 21:34:58   

You can uncheck the check boxes in the refresh dialog to prevent the tables being refreshed - simply tick the boxes for the table that you want to add.

Matt

AlbertK
User
Posts: 44
Joined: 23-Dec-2009
# Posted on: 08-Jul-2011 23:48:46   

Thanks Matt. I didn't realize you could do this. I recall in some older version, if you unchecked the tables during refresh, it removed them from the project. That's no longer the case, which is good news. Thanks.

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 09-Jul-2011 08:16:27   

AlbertK wrote:

I recall in some older version, if you unchecked the tables during refresh, it removed them from the project. That's no longer the case, which is good news. Thanks.

You are right. If you do a catalog refresh and uncheck entities, they are considered removed from the catalog. The entity model will remain but without mapping information for those unchecked entities. Sorry, we mis-understand the question.

In short: you can do a partial refresh but the unchecked entities are considered removed, so It's not like a partial refresh really. IMHO this is like for the sake of the model integrity. Even if 'partial refresh' would be possible and you do minor changes in your DB and you don't remember to check those tables in a refresh, this could break your code. Doing a full refresh should not be a pain anyway. Btw, we are looking into you TypeConverter oddity at the other thread.

David Elizondo | LLBLGen Support Team