Drivers should generally allow "dangling" statements and record readers #3815
Description
What feature or improvement would you like to see?
We should allow you to close a statement even if the record reader is not drained, and close a connection even if statements are not closed. Currently this is considered unsafe and various bindings guard against this. Instead the driver should be prepared and invalidate the statement/readers.
I think, however, the API user should still be expected to Release the statement/reader to avoid leaking memory. But leaking memory is better than crashing.