Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POWhy is EF4 Code First so slow when storing objects?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCraig Stuntz
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThen I'm having doubts about the use of EF. When you're app relies on a very complex Model (domain objects) then I'd prefer an oo database (like db4o). But when the data is mainly tabular you would use a traditional relational database with, and optionally an OR/M like EF. But as you say EF fails when you do heavy bulk load/inserting/updating. So what I was afraid of is actually true. EF4 is only an option when doing very light database operations, and you're stuck to using a relational database.
      singulars
      1. PO
      1. USSaab
    2. COAgain, not just EF, but *any* ORM will be slower than a DB server's bulk loading features. The EF may be slower than ORMs which support bulk inserts, but even those won't be as fast as the streaming APIs used on DB server dedicated bulk loading features. Bulk loading is a corner case for most apps, but if it's your bread and butter then you'd do better to use something like SSIS than an ORM.
      singulars
      1. PO
      1. USCraig Stuntz
    3. COI agree that most of the OR/M's will be slower that just bulk loading. But I have to disagree that an OR/M couldn't also make use of the bulk loading features of a database. The code is very easy to generate. But I think something is going wrong with EF4 Code First. Since just adding the Recipe entity to the dbContext takes a lot of time (130 seconds). Storing in the database (dbContext.Recipes.SaveChanges) is not a speed demon either, 70 seconds for 50.001 rows. Which translates into 50.000/70 = 714 row/s.
      singulars
      1. PO
      1. USSaab
 

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