Brian Kelley wrote:
My guess is the storage is going out of scope and being garbage collected and thereby closing your views without you knowing about it. You should keep the storage object in scope for your entire application run.
Spot on, I think.
< snip>
So at some point, the only way out I could think of is to make views act as being empty. All "rows" continue to exist, they just don't have any properties anymore. Which does indeed make them pretty useless, but at least it leads to well-defined semantics.
A possible solution to the python wrapper would be to have all views keep a reference to the initial storage or the storage from the view that created it. This would be a minor fix I think.
The way to avoid problems in Python, is to store the storage object in a variable which is guaranteed to stay around as long as its data needs to be accessed.
Yep.
-jcw
_______________________________________________ metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
_______________________________________________ metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
