> Within the boundaries of my understanding, this recipe should work... > the PRESERVE ROWS option leaves the table for the whole session, > otherwise it would get destroied a microsecond later with the first commit.
I doubt it works. How do you ensure that you get the proper user when several users access your site at once, creating/overriding rows in that temporary table of yours? What _could_ work is to enhance that table with a session-id column, and somehow obtain a session id from the current connection inside the database. But this actually is a postgres-question. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
