Re: Some basic session state questions
- From: codegreen9@xxxxxxxxx
- Date: 10 Apr 2006 11:47:31 -0700
Thanks very much for the replies.
Hans: Thanks for the info. Also, the .aspnet group would have been
more appropriate, thanks for mentioning it. Is it a common (or
advisable) practice to save and restore the Page object itself
(InProc)?
Michael: Thanks for pointing out Session_End. For this project, I have
a reason to use SQL other than simply as a mechanism for storing
session info. The reason for storing info in SQL would be to set up
another stored procedure call that I'll need to do. This boils down to
a "best practices" SQL question. The user will be able to select 1-600
items, which translate into rows in table A. So, I think the "best
practice" option would be to bulk insert the selections into another
SQL table (table B), and use a join to pull out the data from table A,
which could be done with a single stored procedure call. Then I'd need
to clean out table B.
Other options would be making a stored procedure call for every
selection (up to 600, not very efficient), or passing the selections as
an array and parsing (not very relational).
After writing this post, I think I'll end up pulling all rows from
table A once, at the application level (the data is pretty static), and
use DataViews at the session level to let users pick and choose their
data. One SQL stored proc call per day... yeah, i like that better...
:)
.
- References:
- Some basic session state questions
- From: codegreen9
- Some basic session state questions
- Prev by Date: Re: Assembly Event Question
- Next by Date: TabIndex property not working for me
- Previous by thread: Re: Some basic session state questions
- Next by thread: Why doesn't trace write timestamp?
- Index(es):
Relevant Pages
|
