You are better off almost certainly recalculating what you need every time. If
you have pages of data, rerunning the report and then using SQL's rownum to
select out the exact rows needed for each request as it comes in.
Your choice though
--- Peter Dawn <[EMAIL PROTECTED]> wrote:
> nay. j
nay. just a simple web app. where i generate a report based on user
data. this data is generated based on some calculations i perform on
other tables.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [
Is this that chat application? If it is I might seriously ponder using a
persistent JMS store to hold conversation state..
http://www.activemq.org/site/ajax.html
On 9/4/06, Peter Dawn <[EMAIL PROTECTED]> wrote:
am not sure i follow. where am i suppose to store that data.
-
am not sure i follow. where am i suppose to store that data.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
In general a bad idea... you are much better off usually to simply rerun the
query rather than hold some sort of information (esp in a temp table) across
requests.
I would suggest you rethink this...
--- Peter Dawn <[EMAIL PROTECTED]> wrote:
> guys,
>
> i have a tap3 and postgres issue. sorry f
guys,
i have a tap3 and postgres issue. sorry for posting it here, but i was
hoping to get some help from people who actually use tapestry and have
run into this problem.
now my problem is that i am generating a temp table for some
calculations. a temp table is generated when the user accesses a
