I found myself a little bit confused for the similarity between QDSCV & OA functionality so, If anyone could clarify will be great.
I can use QDSCV to Submit, Reject changes as the OA but in a different way.
What is the best approach to go with ...
Best regards
Waleed
4 Answers, 1 is accepted
By QDSCV Do you mean QueryableDomainServiceCollectionView? And if so, this is not something that OpenAccess can replace. The QueryableDomainServiceCollectionView is a class that the RadDomainDataSource uses in order to create queries that are then posted trough WCF RIA Services.
OpenAccess is an ORM tool which means that it is on the other end of the service and handles the actual database operation, and not the client side operations.
Please give us some light on what you are trying to achieve so that we can be of better help.
Serge
the Telerik team
I understand the difference very well.
What I need to clarify is the use of both to Submit or reject changes ...
Best regards
Waleed
I think you could find the following sections of the OpenAccess documentation useful for this scenario:
http://www.telerik.com/help/openaccess-orm/getting-started-root-quickstart-sl-overview.html
http://www.telerik.com/help/openaccess-orm/getting-started-root-quickstart-sl-wcfria-overview.html
http://www.telerik.com/help/openaccess-orm/getting-started-root-quickstart-sl-wcfdata-overview.html
They cover the usage of OpenAccess in different services scenario with Silverlight. These examples should give you some perspective on where the storage of OpenAccess actually happens and how the services interact with our product.
Zoran
the Telerik team
I can tell that the QDSCV is used to submit/reject changes to your domaincontext, but you will find it terrible to trace/handle the exceptions. The OA is used in this regards.
Best