Windows should execute commands asynchronously

BWendling

Member³
I often start long running processes through the Edit table window or the Program Window for example building an index, compiling a program.

At the moment, this will freeze the GUI until the DB comes back. This should be changed to send the DB command asynchronously (as you already do in the SQL window).
 
I agree, this does rot. However, you can view SQL from the edit page once you've made your changes, and then paste them into a command window to get them to execute asynchronously. It has the added benefit of allowing you to see your progress if you have multiple commands to execute, as well as allowing you to tweak the statements for things the gui doesn't allow for (parallel, nologging, etc.)

hth
 
I have added this to the list of enhancement requests. It requires that table modifications run in a separate session, but this should not be a problem.
 
Back
Top