<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Tools / SQL dialog is modal" href="https://bugs.documentfoundation.org/show_bug.cgi?id=66813#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Tools / SQL dialog is modal" href="https://bugs.documentfoundation.org/show_bug.cgi?id=66813">bug 66813</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>(In reply to Lionel Elie Mamane from <a href="show_bug.cgi?id=66813#c11">comment #11</a>) > 3.2) Try to run a long-standing SQL command in the "Tools/SQL" dialog, then > try with the mouse in the UI to force execution of another SQL command > (easiest is double-click on a query or on a table). > 4) What happens in 3.2? The best would be that the UI just waits for the > dialog command to finish, then does the requested thing. What might happen > instead is that the SQL command from the dialog is aborted. I just had a thought for why the dialog may have been made modal in the first place. Is there by any chance any requirement to release/get a mutex from any other active component of the database connection or have some other form of synchronisation ? For example, say I have a Form saved outside of the ODB file, pointing to a DB instance and opened for input, and I have my SQL dialog open within an ODB container pointing to the same DB instance at the same time - which one takes precedence if I execute 2 SQL operations at the same or pseudo-same time ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>