Ok, so you'd basically be destroying the dbase cursor for the background task so that it is unusable.

That will work, I think, but it will mean that you can't access the dbase from the background task at all - unless you open a new dbase connection for the background task - which is exactly what we did with our patch.  But if you do that, then the gotcha still exists: any dbase info accessed with the new connection will be old data from before the original connection existed.  I don't think there is any way around the gotcha: it just has to be coded around.

- Berwyn

Aaron Swartz wrote:
 Hi Anand.  I'm not sure exactly what you mean by db dereferencing.  Can you
elaborate?
    

He means no longer having a variable point to it, so that it gets
garbage collected.



  

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to