Databases
StackOverflow2013
Postsdbo
POTime to start returning IQueryable<T> instead of IList<T> to my Web UI / Web API Layer?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTime to start returning IQueryable<T> instead of IList<T> to my Web UI / Web API Layer?
    primarykey
    data
    text
    <p>I've got a multi-layer application that starts with the repository pattern for all data access and it returns IQueryable to the Services layer. The Services layer, which includes all of the business logic, returns IList to the Controllers (note: I'm using ASP.NET MVC for the UI layer). The benefit of returning IQueryable in the data access layer is that it allows my repositories to be extremely simple and the database queries to be deferred. However, I'm triggering the database queries in my services layer so that my unit tests is more reliable and I don't give flexibility to the Controllers to reshape my queries. However, I've recently encountered several situations where deferring the execution of queries down to the Controllers would have been significantly more performant because the Controllers had to do some projections on the data that was UI specific. Additionally, with the emergence of things like oData, I was starting to wonder if end points (e.g. web UI or web apis) should be working directly with IQueryable. What are your thoughts? Is it time to start returning IQueryable from the services layer to the UI layer? Or stick with IList?</p> <p>This thread here: <a href="https://stackoverflow.com/questions/718624/to-return-iqueryablet-or-not-return-iqueryablet">To return IQueryable&lt;T&gt; or not return IQueryable&lt;T&gt;</a> seems to vouch for returning IList to the UI layers, but I was wondering if things are changing because of new emerging technologies and techniques.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USJohnny Oshika
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTime to start returning IQueryable<T> instead of IList<T> to my Web UI / Web API Layer?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTime to start returning IQueryable<T> instead of IList<T> to my Web UI / Web API Layer?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POTime to start returning IQueryable<T> instead of IList<T> to my Web UI / Web API Layer?
      1. USRobert Harvey
      1. VTFavorite
    1. COActually the thread you linked is agnostic; it doesn't favor one way or another. Test-driven developers are always going to favor *fixing* the interface, so that it is more predictable. Personally, I like the flexibility and lazy execution of IQueryable. You can always call ToList() right before you plunk it into the UI.
      singulars
      1. POTime to start returning IQueryable<T> instead of IList<T> to my Web UI / Web API Layer?
      1. USRobert Harvey
 

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