On 15 Jan 2016, at 4:20pm, Olivier Mascia <om at integral.be> wrote:
> I'm only left with the case of a row returning query which the programmer > would not want to step() up to the end. In this case, it is very reasonable > to have the programmer think of "freeing" the query in some way through > either the Statement class going out of scope or the call of some "reset()" > method. This is a common problem when you're writing a library. Assuming that you can provide a _dispose() method which is automatically called when your object slips out of scope, you're fine: just call _finalize() in it. If you cannot depend on this then you are going to have to provide a disposal method and rely on your programmer calling it. Simon.
