Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>without any code from the controllers it's difficult to say, but a very common problem with Entity Framework is forgetting to use the <code>.Include()</code> extension method. e.g. <code>var cameras = db.Cameras.Include(c =&gt; c.Features).ToList();</code> which would give you a list of Cameras and associated features to pass to your view.</p> <p>Also, if you add the virtual keyword to your Navigation Properties, Entity Framework can perform "Lazy Loading" where it automatically loads the associated items the first time they are accessed (server side). In general, most Navigation Properties would also be defined as generic. e.g.:</p> <pre><code>public class Feature { public int ID { get; set; } public string Desc { get; set; } public virtual ICollection&lt;Camera&gt; Cameras { get; set; } } public class Camera { public int ID { get; set; } public string ModelName { get; set; } public virtual ICollection&lt;Feature&gt; Features { get; set; } } </code></pre> <p>This allows you access to a much larger array of extension methods for filtering and sorting. <code>IEnumerable</code> describes behavior, while <code>List</code> is an implementation of that behavior. When you use <code>IEnumerable</code>, you give the compiler a chance to defer work until later, possibly optimizing along the way. If you use <code>List</code> you force the compiler to reify the results right away. In your case, using ICollection vs IEnumearable is necessary, since IEnumerable only allows list browsing, while ICollection defines a CopyTo method used by Entity Framework Internally.</p>
    singulars
    1. This table or related slice is empty.
    1. POMVC 4: Displaying a List<> property on a view
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USClaies
    1. USClaies
    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. This table or related slice is empty.
    1. COYou were right, no Include()... but when I use "return View(db.Cameras.Include(c => c.Features).ToList());" in the controller, I get the error "A specified Include path is not valid. The EntityType 'MyApp.Models.Camera' does not declare a navigation property with the name 'Features'." even tho Intellisense shows the property in its dropdown and it is defined as you illustrated above. Guess I missed something?
      singulars
      1. PO
      1. USdavecove
    2. COactually it was my mistake, since you have 2 collections referencing each other, you need to use ICollection<T> rather than IEnumerable<T>. I'll update the answer.
      singulars
      1. PO
      1. USClaies
 

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