Thank you for getting back to me so quickly and I apologize for not doing the same. I have a requirement which basically states that for reusable objects, the next user of that object must not be able to access any residual data from the previous user. Residual data needs to be cleared from an object before another it is assigned to another process/user. One area of concern with respect to this is database connection pools. Caching is another one, but the documentation is clear on how to mitigate that risk.
On Tuesday, May 28, 2013 12:30:29 PM UTC-7, Massimo Di Pierro wrote: > > Web2py closes the transaction and stores the connection object. Nothing is > cleared out. Should it be? To my knowledge there is nothing specific the > developers should do before the connection is returned to the pool. It is > possible that I am missing something here... > > On Tuesday, 28 May 2013 13:26:28 UTC-5, [email protected] wrote: >> >> Hello, >> >> I am a relatively new web2py user. I've read the on-line documentation >> and looked within this forum and cannot find my answer. I am wondering >> about database connection pools. What does web2py do when releasing a >> database connection back into the pool? What gets cleared out, if >> anything? Is there something developers should call when done with the >> connection prior to web2py returning it to the pool? >> >> Thank you, >> >> -- Maryanne >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
