Best Practices - three tier arhitecture, sort and pagination

Question

0.00/5 (No votes)

See more:

i have three tier arhitecture in web app (asp.net)

should sort and pagination be in presentation layer or business logic?

C#

//Search.aspx.cs
public void SearchProjects(int recordCount)
{
    var data = DAL.GetData();

    var filtered = data.OrderBy(x => x.Key).Take(recordCount);

    //todo
}

or

C#

//Search.aspx.cs
public void SearchProjects(int recordCount, object sortType)
{
    var data = DAL.GetData(recordCount, sortType);

    //todo
}

Posted 10-Nov-15 3:37am

Hanzaplast

Add a Solution

Comments

Richard Deeming 10-Nov-15 10:20am

Does the GetData method return an implementation of IQueryable<>?

If not, doing the sorting and paging in the calling code will be extremely inefficient.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Answer 1 · 2015-11-10T04:26:00

"It depends". What does GetData return? If it returns an IQuereable or IEnumerable such that the query hasn't yet been issues by the time it gets to the presentation layer then you could do the paging\sorting at the presentation layer.

If GetData actually retrieves all data and returns it as an in-memory datastore like DataSet, List<t> etc then you shouldn't page\sort in the presentation layer.

Getting back to the first scenario...if GetData returns IQuereable then you could consider that bad design as you are tightly-coupling your presentation layer to the data layer as your presentation code can only work with datastores that support lazy-loading via IQuereable. It means that your presentation layer will often need knowledge of the data store to do its work. If GetData reads all the rows into an in-memory data store and returns that then you don't have those issues, however your paging\sorting will need to be done at the data layer.