Type converters get removed from all entities/fields after refreshing model from database

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

I'm using 3.1 designer (Feb 7, 2011 build) and I noticed that type converters get removed from all entities/fields after refreshing model from database. Is there some setting that would prevent this from happening?

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

I'm afraid I couldn't duplicate this using the latest version of 3.1 - my type converters stayed attached to my entities. Please could you download and try the latest version of 3.1 and let us know if this resolves the issue ?

Thanks

Matt

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 07-Jul-2011 21:48:49   

Did fields in the database change type? This could be a reason the type converters were removed.

Frans Bouma | Lead developer LLBLGen Pro
AlbertK
User
Posts: 44
Joined: 23-Dec-2009
# Posted on: 08-Jul-2011 23:40:58   

The May13th build does not have this issue, so must have been a bug. Thank you!

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

Actually, it ALMOST works. If you do a full refresh - type do not get removed. That's good. But if you do a partial refresh (i.e. uncheck tables that you don't want refreshed), it will drop type converters from those objects that did not get refreshed. disappointed

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 09-Jul-2011 07:57:58   

If you do a partial refresh, all unchecked elements will be considered removed from the relational model data. Are you sure you want that? Even with that, removed entities from rel. model data are not removed from your model, but the field mappings are removed (because there is no rel.model data information for that entities), but the TypeConverterToUse remains in the entity filelds.

So I can't reproduce it. BTW the latest build is June 17th, not May 13th.

David Elizondo | LLBLGen Support Team