Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>IQueryable</code> is used when you are using Linq-to-entities = you are building declarative LINQ query in your application which will be interpreted by LINQ provider as SQL and executed on the server. Once the query is executed (iterated) it will turn to become IEnumerable and objects will be materialized as needed for iteration = not immediately.</p> <p>Once you call stored procedure you are not using Linq-to-entities because there is no declarative query built in your application. The query / SQL already exists on database server and you are just invoking it. This will return <code>IEnumerable</code> but again it will not materialize all results immediately. Results will be materialized as iterated. This is principle of database cursor / or .NET data reader when you explicitly ask for fetching object.</p> <p>So if you call something like this:</p> <pre><code>foreach (var keyword in dbContext.FindCoursesWithKeywords(keywords) .Select(l =&gt; l.Value)) { ... } </code></pre> <p>You are fetching courses one by one (btw. why to load whole course if you are interested only in keywords?). Until you complete or break the loop your data reader is opened to fetch records.</p> <p>If you instead call this:</p> <pre><code>foreach (var keyword in dbContext.FindCoursesWithKeywords(keywords) .ToList() // or ToArray .Select(l =&gt; l.Value)) { ... } </code></pre> <p>You will force query to materialize all results immediately and loop will perform on collection in memory instead of opened database reader.</p> <p>Difference between <code>IEnumerable</code> and <code>IQueryable</code> is not in the way how data are fetched because <code>IQueryable</code> is <code>IEnumerable</code>. The difference is in backing construct (something must implement these interfaces). </p>
    singulars
    1. This table or related slice is empty.
    1. PO.NET Entity Framework - IEnumerable VS. IQueryable
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLadislav Mrnka
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO.NET Entity Framework - IEnumerable VS. IQueryable
      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. VTAcceptedByOriginator
    1. COHi, thanks for this explanation! So since this is a stored proc it won't return an IQueryable, as it doesn't support all the features that a query does, right? (btw, I'm fetching courses not keywords) :)
      singulars
      1. PO
      1. USjustabuzz
 

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