Thank you for your feedback.
We are using LINQ only for reading data from the database and this covers only the Read part of the CRUD acronym.
I am not sure how to use LINQ for Create, Update or Delete scenarios.
Getting back to the Read scenario I can offer you some alternatives that do not require LINQ and produce clean and nice code and results:
- You can use lazy loading of related entities. For example if a Customer has Address, you can load the customer and then access the Address property. OpenAccess will populate the data for the proper Address record automatically for you.
- You can load related entities eagerly if you define a Fetch Strategy. This will enable OpenAccess to generate the right statements to load the specified related objects in single query (if possible). You can find more about Fetch Strategies here.
I hope that the information above will enable you to complete your programming tasks easier.
If you have any additional comments or question do not hesitate to contact us again.
the Telerik team
Telerik OpenAccess ORM Meets ASP.NET Web API. Read more.