Beginners Question

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
tbriggs
Posts: 1
Joined: Tue 11 Oct 2011 20:33

Beginners Question

Post by tbriggs » Tue 11 Oct 2011 20:48

With EF 4.1

When you have a conceptual model, source code and a database schema:

Do edits at any of these three levels automatically propagate to the remaining levels?

If not, what directions of propagation exist?

I'm guessing there is no short answer :)

Thank you in advance!

wgkwvl
Posts: 39
Joined: Tue 20 Jul 2010 15:13

Post by wgkwvl » Wed 12 Oct 2011 07:56

quote : 'I am guessing there is no short answer'

Yes

Shalex
Site Admin
Posts: 8247
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Wed 12 Oct 2011 15:07

tbriggs wrote:When you have a conceptual model, source code and a database schema:
Do edits at any of these three levels automatically propagate to the remaining levels?
If you use the EF approach with the *.edml/*.edmx file, there are three parts of the model: CSDL, SSDL, MSL ( http://msdn.microsoft.com/en-us/library ... =VS.110%29 ). We recommend using the Devart Entity Developer tool that allows editing both CSDL and SSDL parts of your model in design time.
tbriggs in e-mail wrote:There are approxamatly 700 Oracle tables
1. Please take into account that usage of any ORM tool with such huge model causes the performance losses comparing to a plain ADO.NET. We recommend you the following best practices to optimize your approach:

- use the Devart Entity Developer tool (the Devart Entity Model template in VS, *.edml), not Entity Designer (ADO.NET Entity Data Model, *.edmx). Entity Developer is optimized for working with Oracle metadata (helps when using the Update To Database and Update From Database functionality)

- make your model better understandable with Large Model Splitting: http://www.devart.com/blogs/dotconnect/ ... loper.html

- such big model leads to very time-consuming first query in AppDomain because of view generation ( http://msdn.microsoft.com/en-us/library/cc853327.aspx ). This problem can be solved partially with view pregeneration ( http://www.devart.com/entitydeveloper/large-models.html )

- if you choose the Code-First (EFv4) approach, refer to
http://www.devart.com/blogs/dotconnect/ ... qlite.html
http://www.devart.com/blogs/dotconnect/ ... plate.html

2. We also recommend you to try LinqConnect ( http://www.devart.com/linqconnect/ ) instead of Entity Framework. LinqConnect includes the same Devart Entity Developer tool, and its run-time is more light-weight. LinqConnect should work faster with a large model.

Post Reply