Re: Wrong results
From: Adam Machanic (amachanic_at_hotmail._removetoemail_.com)
Date: 08/10/04
- Next message: M K: "Re: Query to split one table into 2"
- Previous message: simon: "Re: Wrong results"
- In reply to: simon: "Re: Wrong results"
- Next in thread: simon: "Re: Wrong results"
- Reply: simon: "Re: Wrong results"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Aug 2004 09:43:19 -0400
Why store the value at all? Is it that expensive to calculate? Could you
cache it in your web server's memory instead of relying on SQL Server?
If you absolutely must store it in the database, perhaps you should consider
using a table that stores rows on a per-user rather than per-application
basis?
So instead of:
Orders
----------------------
ProductId Quantity
You could have:
Orders
-----------------------------------------
UserId ProductId Quantity
This would help ensure that users don't collide with each other.
"simon" <simon.zupan@stud-moderna.si> wrote in message
news:OOIGO6tfEHA.556@tk2msftngp13.phx.gbl...
> Yes.
> It's some kind of statistic. When user request the statistic, I calculate
> the values and put them in one table.
> Then I show the results from that table to user. If user click some kind
of
> filter on the page or sort, then I just read again from that table with
> different sort or filter option. I don't calculate again.
- Next message: M K: "Re: Query to split one table into 2"
- Previous message: simon: "Re: Wrong results"
- In reply to: simon: "Re: Wrong results"
- Next in thread: simon: "Re: Wrong results"
- Reply: simon: "Re: Wrong results"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|