Linq query continue loading MVC table 88 lakh records there not working

Question

1.00/5 (2 votes)

See more:

(No description provided by OP)

What I have tried:

C#

var assetDepDetailList = (from ad in assetDepDetQuery
    where ad.AssetID == ad.AssetID
    select new { ad.AssetDepreciationDetailID, ad.AssetID, ad.AssetDepUpTo }).ToList()
    .Select(f => new AssetDepreciationDetail()
    {
        AssetDepreciationDetailID = f.AssetDepreciationDetailID,
        AssetID = f.AssetID,
        AssetDepUpTo = f.AssetDepUpTo
    }).ToList();

Posted 1-Dec-20 1:13am

Member 11090998

Updated 1-Dec-20 5:35am

Richard Deeming

v2

Add a Solution

Comments

F-ES Sitecore 1-Dec-20 7:34am

"not working" doesn't give anyone enough information to know what the issue is. What doesn't happen that you expect to happen, or what does happen that you didn't?

Richard MacCutchan 1-Dec-20 7:41am

88 lakh is 8,800,000!
Trying to access that many records in one go is a recipe for disaster. Add some criteria to reduce the number to a more manageable amount (less than 1000).

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)

OriginalGriff · Answer 1 · 2020-12-01T01:47:00

The problem is simple: you are designing a UI so it is easy for you to implement, instead of easy for the user to work with.

Imagine it did work, and you are a user. You are faced with a table that - when it eventually manages to load - contains nearly 9,000,000 items. How long is it going to take you to find the one row you are actually interested in? Hours? Days? Weeks?
Or are you - the user - going to say "Sod this for a game of soldiers. I'm off to a site that works."

The answer is always going to be the latter. Every. Damn. Time.

Change your whole UI to be user friendly, or nobody will visit your site twice.
Show a maximum of 100 items on a page, and let th user search, filter, and page the data to help him find what he needs. Just throwing the data at him as if you don't care and expecting him to sort it out is a waste of time: his and yours.