> hm...what is the usecase for binding a Results instance as
> instance attribute? I can not think of a case where this would
> make sense.
1. I have a view for a content object, which execute an SQL
query and stores the results as an instance of the view, which
should be only for the life of the request. However, due to
this bug, the view and all associated objects (the request,
the SQL results, etc.) leak.
2. I can also imagine this being problematic for caches of the
SQL results.
Andreas wrote:
> hm...what is the usecase for binding a Results instance as
> instance attribute? I can not think of a case where this would
> make sense.
1. I have a view for a content object, which execute an SQL
query and stores the results as an instance of the view, which
should be only for the life of the request. However, due to
this bug, the view and all associated objects (the request,
the SQL results, etc.) leak.
2. I can also imagine this being problematic for caches of the
SQL results.