This question is locked. New answers and comments are not allowed.
abdu bukres
Top achievements
Rank 1
Rank 1
abdu bukres
asked on 01 Aug 2010, 07:16 PM
The OpenAccess vs EF4 comparison matrix shows that POCO is not supported. Is this true?
http://www.telerik.com/products/orm/openaccess-vs-entity-framework.aspx
http://www.telerik.com/products/orm/openaccess-vs-entity-framework.aspx
5 Answers, 1 is accepted
0
IT-Als
Top achievements
Rank 1
Rank 1
answered on 02 Aug 2010, 06:50 AM
Hi abdu,
I think it depends on how you define POCO support.
Yes, in OA you can a turn a POCO into a persistent capable object by decorating it with the Persistent attribute.
On the road map you can also see an item called DTO (data transfer object), which essentially (as far as I have understood it) is a POCO (that may have tracking capabilities).
So (as always) it depends :-)
How do you define POCO support?
Regards
Henrik
I think it depends on how you define POCO support.
Yes, in OA you can a turn a POCO into a persistent capable object by decorating it with the Persistent attribute.
On the road map you can also see an item called DTO (data transfer object), which essentially (as far as I have understood it) is a POCO (that may have tracking capabilities).
So (as always) it depends :-)
How do you define POCO support?
Regards
Henrik
0
abdu bukres
Top achievements
Rank 1
Rank 1
answered on 02 Aug 2010, 04:50 PM
I haven't used OpenAccess and so I don't know how the relationship between classes and the persistent layer and functionality are defined. POCO is your regular classes which define your model without any knowledge of your persistent layer.
0
Hi abdu bukres,
Poco has some positive things like independence but also has negative effects like lazy loading and change tracking are not working well, reflection has to be used to read and write data, what is slow.
The OpenAccess approach is to make backend dependent class definitions necessary where you are close to the server and performance counts. As soon as you need poco, for data transport or n-tier applications we provide a generated poco model for you to fulfill your needs. If you are scared about the independence of your layer in a fat client or applications server tier, the recommended way is to use interfaces on top of the persistent model instead of a slower poco model.
All the best,
Jan Blessenohl
the Telerik team
Poco has some positive things like independence but also has negative effects like lazy loading and change tracking are not working well, reflection has to be used to read and write data, what is slow.
The OpenAccess approach is to make backend dependent class definitions necessary where you are close to the server and performance counts. As soon as you need poco, for data transport or n-tier applications we provide a generated poco model for you to fulfill your needs. If you are scared about the independence of your layer in a fat client or applications server tier, the recommended way is to use interfaces on top of the persistent model instead of a slower poco model.
All the best,
Jan Blessenohl
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
0
abdu bukres
Top achievements
Rank 1
Rank 1
answered on 03 Aug 2010, 04:53 PM
Is there sample code or application which exhibits this kind of interfaces?
0
Hi abdu bukres,
There is in fact a knowledge base article that you can use as a guide to using interfaces with OpenAccess. Please note however that interfaces are only supported while using forward mapping. They are not yet a part of the new Domain Model, we are currently working on them.
Serge
the Telerik team
There is in fact a knowledge base article that you can use as a guide to using interfaces with OpenAccess. Please note however that interfaces are only supported while using forward mapping. They are not yet a part of the new Domain Model, we are currently working on them.
I hope this is what you are looking for, if not please contact us back.
Serge
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