Databases
StackOverflow2013
Postsdbo
POMoving from ADO.NET to ADO.NET Entity Framework
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMoving from ADO.NET to ADO.NET Entity Framework
    primarykey
    data
    text
    <p>I am web developer for nine years now. I love to develop custom CMS and purly hand coded web applications.</p> <p>I was ok with ADO.NET Data Access model, writting native SQL Queries to the database and calling store procedures via DBCommand.</p> <p>2 years now i was thinking to move to ADO.NET Entity Framework.</p> <p>I know there are alot of advantages in terms of productivity but i really don't like/understand the way it work Entity Framework.</p> <p>In terms of productivity i have create an application that auto generates for me the ADO.NET Code so i don't waste mutch time to code ADO.NET code.</p> <p>Should i move on Entity Framework?</p> <p>PS : I am a performance lover.:P</p> <p>PS 2 :For example, How can i implement a Modified Preorder Tree Traversal to manage hierarchical data (ex : Categories of products) in Entity framework?</p> <p>PS 3 : I Work with MySql Server</p> <hr> <p><strong>Edit</strong></p> <p>After a bit of reading, i understand that ADO.NET Entity Framework is wonderful.</p> <p>It give us alot of benefits that we have to hand craft or "copy-paste" in the past. Another benefit that comes with it is that is completely Provider independent. Even if you like the old ADO.NET micanism or you are a dinosaur like me(:P) you can use the entity framework using the EntityClient like SqlClient, MySqlClient and use the power of Entity-Sql witch is provider independent.</p> <p>Yes you loose some performance. But with all these cache technologies out there you can overcome this.</p> <p>As i always say, "The C is fast, the Assembly even more...but we use C#/VB.NET/Java"</p> <p>Thank you very mutch for the good advices.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSanosay
    1. USSanosay
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMoving from ADO.NET to ADO.NET Entity Framework
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMoving from ADO.NET to ADO.NET Entity Framework
      1. USFMFF
      1. VTFavorite
    1. COI may get flamed for this, but I jumped into ORMs about a year ago. Last month I made the decision to jump back out again. You lose a lot of control over your code, and any custom functionality that is not supported out of the box is ridiculously complex to do... the time you save right off the bat ends up getting eaten up by trying to get things that should be simple to work just a little ways in. For me, moving to ORMs was a big mistake that I'll continue to pay for until I can replace it with nice, clean, fully controllable ADO.NET controls again.
      singulars
      1. POMoving from ADO.NET to ADO.NET Entity Framework
      1. USJeremy Holovacs
    2. COJeremy...i just loved your answer! Thats exactly the reason i afraid of.
      singulars
      1. POMoving from ADO.NET to ADO.NET Entity Framework
      1. USSanosay
    3. CO@JeremyHolovacs - While it's true that some frameworks have limitations, 99.9% of the time I see someone say this it's because they don't know how to do something in the framework, not because the framework doesn't allow it. You have a lot of knowledge in the old solution, and none in the new.. of course you will be frustrated when you think "I could have done that in 5 minutes in blah", but that's just your lack of knowledge getting in the way, not the tool.
      singulars
      1. POMoving from ADO.NET to ADO.NET Entity Framework
      1. USErik Funkenbusch
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload