You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Long-running operations can block the client unintentionally (e.g., a query where millions of results are returned and LIMIT was forgotten). CTRL+C in this case would be the natural way of aborting this. Right now, CTRL+C kills the client, without a warning or a clean exit. If no command is running, CTRL+C already behaves well (exist on empty prompt, clearing prompt if non-empty); this should be kept.
The text was updated successfully, but these errors were encountered:
mkroetzsch
changed the title
Client: CTRL+C should stop current operation rather than kill the client
[client] CTRL+C should stop current operation rather than kill the client
Oct 2, 2020
Long-running operations can block the client unintentionally (e.g., a query where millions of results are returned and LIMIT was forgotten). CTRL+C in this case would be the natural way of aborting this. Right now, CTRL+C kills the client, without a warning or a clean exit. If no command is running, CTRL+C already behaves well (exist on empty prompt, clearing prompt if non-empty); this should be kept.
The text was updated successfully, but these errors were encountered: