https://bugs.freedesktop.org/show_bug.cgi?id=80084
--- Comment #1 from Lionel Elie Mamane <[email protected]> --- The difficulty is (from XStatement documentation): All statement execute methods implicitly close a statement's current ResultSet if an open one exists. To do that, we need to keep (at least a *weak*) reference. Which is what many drivers actually do... Also (from service ResultSet documentation): A ResultSet is automatically closed (disposed) by the Statement that generated it when that Statement is closed, re-executed, or used to retrieve the next result from a sequence of multiple results. So actually, contrary to the assumption in commit d87c2c59c9c1d5f5825f355c9eb941fdf95b42f6, the resulset is not allowed to survive the statement that generated it. That commit needs to be partially reverted, but partially only: it still needs to "abandon" close ownership of the generated resultset and generate a *fresh* one each time it is asked for one by execute() (but not necessarily in the case of repeated calls to getResultSet()). -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
