Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think this is a timely question, as I was wondering the exact same thing. I am trying to create a serious e-commerce model and I am trying to keep my POCOs free of persistence concerns as well as trying to stay true to Domain Driven Design. So far, I am very wary, and I am on the fence about whether I should jump ship to NHibernate. The only thing keeping me from doing so is that I assume that Microsoft will improve (and quickly).</p> <p>Some of the biggest problems so far:</p> <ul> <li>Inability to finely control object materialization. EF calls the zero-arg constructor on your POCO, and this is a behavior you cannot change.</li> <li>No enum support. The community has been screaming -- screaming! -- for this, and it hasn't happened. The workarounds are terrible, and pollute your domain model.</li> <li>Weird mapping bugs when trying to control column names and relationships in the database. The main ones I can think of are with compound keys and many-to-many relationships. These can be worked around, and I assume these will be fixed by release time, but they are frustrating nonetheless.</li> <li>Bad SQL. I also do DBA work, and the SQL that EF generates (with or without Code-First) is atrocious.</li> </ul> <p>And this is just the tip of the iceberg: I am only starting to learn EF4 and I'm running into awful roadblocks. As I think of more reasons, I'll add them here. I'm still struggling through it.</p> <p>(I wonder whether the community will give it another vote of "no confidence.")</p> <hr> <p>More:</p> <ul> <li>To add to the "Weird mapping bugs" problem: You cannot control the name of a column if it participates in a self-referencing relationship (for example, if you have a hierarchy). I assume this will be fixed in the final release.</li> <li>Lack of batching, resulting in multiple roundtrips to the database. For example, how do you delete a bunch of items from a collection? <i>Load all entities into memory and delete them one at a time.</i> A smaller gripe is the number of DB hits when inserting into tables that participate in an inheritance relationship.</li> <li>No intelligent way to deal with model changes. EF Code-First loves to completely drop your entire database if it needs to change the schema.</li> <li>Few extensibility points. You can literally count on one hand the number of events that EF4 allows you to subscribe to (and Code-First doesn't provide much more).</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow does EF4 compare with NHibernate?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USanon
    1. USanon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow does EF4 compare with NHibernate?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is very interesting and useful. I hope more SO folks comment before trolls close this thread.
      singulars
      1. PO
      1. USSrikar Doddi
    2. COI would like to hear more, too, as I am /very/ conflicted about committing to EF4 Code-first.
      singulars
      1. PO
      1. USanon
    3. COThis is a very good list. All valid points which i have experienced over the past few months. I'd also throw in EF4's lack of `GEOGRAPHY` data type support (SQL Server), and inability to pass user defined table types (also SQL Server) to stored procs. To combat the former, i had to use triggers, to combat the latter i degaraded to classic ADO.NET.
      singulars
      1. PO
      1. USRPM1984
 

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