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 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 > function within my web app. if the user closes the web app, restarts > it and accesses the same content. it generates an error. so my debug > messages tell me that tap can find the table, but cant access it. > > so when the user closes the web app and restarts it, the second > session cannot access the first sessions table. now is there a work > around this. has anybody else run into this problem. i have tried to > read some documentation on it but cant find a solution. the reason i > am using temp tables in the first place was coz i needed to perform > some calculations based on other tables and need to store this > information somewhere. hence the idea of a temp table. > > thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
