This question is locked. New answers and comments are not allowed.
Shane Sholdice
Top achievements
Rank 1
Rank 1
Shane Sholdice
asked on 14 May 2010, 03:05 PM
Hi,
I'm sure there must be an easy way to do what I need but I'm failing to see it. I've carefully decorated properties on my domain classes with Fetch Plan attributes using the forward mapping tool.
The team is actually using Reverse Mapping in our project. Whenever we regenerate the domain layer from the database using the reverse mapping wizard, all of our fetch plan attributes are deleted. We then have to go back and manually add everything back using the Forward Mapping tool following the instructions as outlined in this link http://www.telerik.com/support/kb/orm/general/fetch-groups.aspx
Is there a way to keep fetch plan attributes persistent when using the reverse mapping wizard?
I'm sure there must be an easy way to do what I need but I'm failing to see it. I've carefully decorated properties on my domain classes with Fetch Plan attributes using the forward mapping tool.
The team is actually using Reverse Mapping in our project. Whenever we regenerate the domain layer from the database using the reverse mapping wizard, all of our fetch plan attributes are deleted. We then have to go back and manually add everything back using the Forward Mapping tool following the instructions as outlined in this link http://www.telerik.com/support/kb/orm/general/fetch-groups.aspx
Is there a way to keep fetch plan attributes persistent when using the reverse mapping wizard?
1 Answer, 1 is accepted
0
Hi Shane Sholdice,
We are aware of this drawback. Currently it is not possible to retain the FetchPlan attributes while regenerating the class. We are in the process of implementing an improved FetchPlan API with design-time checks (and not rely on strings) which would be easier to work with.
I'm afraid I cannot provide you with a workaround for the current problem.
We are sorry for the inconvenience caused.
Kind regards,
Ady
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
We are aware of this drawback. Currently it is not possible to retain the FetchPlan attributes while regenerating the class. We are in the process of implementing an improved FetchPlan API with design-time checks (and not rely on strings) which would be easier to work with.
I'm afraid I cannot provide you with a workaround for the current problem.
We are sorry for the inconvenience caused.
Kind regards,
Ady
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.