question on session

Question

0.00/5 (No votes)

See more:

ASP.NET

can we store datareader/dataset in session.if yes which is better and faster

Posted 3-Jan-10 23:03pm

santoshreddy.s

Add a Solution

3 solutions

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)

*dan!sh* · Answer 1 · 2010-01-03T23:14:00

Solution 1

You can store both in session. Storing DataReader in session is of no use, IMHO, since it gives only one time access.

You can store DataSet too but only if it is not too huge.

Posted 3-Jan-10 23:14pm

dan!sh

Matthew Dennis · Answer 2 · 2010-01-04T15:09:00

Do not store a DataReader in session. A DataReader is only of use for forward only iteration of a query response. As such, it must be open. If you store an open DataReader in session, the connection ( as scarce resource) will be held by the DataReader.

Read the DataReader into some data structure, such as a DataReader, before storing in session.

Now comes the next problem, if the data you are storing is large, each user session could store this data.

I would recomment using the Cache instead. You can set a timeout on how long it is stored and you could share the data between users if they all need the same result for the same query parameters.

Christian Graus · Answer 3 · 2010-01-04T15:44:00

Assuming your site will be used by more than 3 people, the approach taken by competent developers would be to never use the session if at all possible. Put an id on the query string and use that to read the data from your data source. This means you can bookmark pages and they will work out how to load themselves with the data that was bookmarked. If you MUST use the session, use it to store an id, and still read it from the data source.

question on session

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0