Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ctrl+C to cancel queries [CORE704] #1076

Closed
firebird-automations opened this issue Apr 4, 2004 · 12 comments
Closed

Ctrl+C to cancel queries [CORE704] #1076

firebird-automations opened this issue Apr 4, 2004 · 12 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @asfernandes

Is related to QA105

Attachments:
firebird-2.1.0.13360-isqlint.patch
firebird-2.1.0.13360-isqlint.patch

SFID: 929233#⁠
Submitted By: asfernandes

At this moment, pressing Ctrl+C in ISQL causes the
program termination.
Is more useful if Ctrl+C cancel the running query (i.e.
abort the output display).

Adriano.

Commits: ad4113e

@firebird-automations
Copy link
Collaborator Author

Commented by: @mkubecek

Patch against 2.1.0.13360: if isql is interactive, SIGINT interrupts a query (only select). For non-interactive isql, program is terminated.

@firebird-automations
Copy link
Collaborator Author

Modified by: @mkubecek

Attachment: firebird-2.1.0.13360-isqlint.patch [ 10021 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @mkubecek

Fixed wrong initial value of Interrupt_flag.

@firebird-automations
Copy link
Collaborator Author

Modified by: @mkubecek

Attachment: firebird-2.1.0.13360-isqlint.patch [ 10022 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Thanks Michal!
I'll write Windows code and commit together.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

Michal, at first glance I've think your patch is posix specific, but it works in Windows too.
But testing in Windows, second Ctrl+C causes process termination without entering in query_abort.
So I've changed it to call SetConsoleCtrlHandler returning appropriate value at query_abort and everything works correctly.

I do have only one comment, why remove "#⁠include <signal.h>"?
We use signal and SIGINT, should it really be removed?

@firebird-automations
Copy link
Collaborator Author

Commented by: @mkubecek

It is not removed, it was included twice: once unconditionally and once depending on HAVE_SIGNAL_H. So I removed first #⁠include and left only the second (conditional).

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 [ 10041 ]

assignee: Dmitry Yemanov [ dimitr ]

SF_ID: 929233 =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

assignee: Dmitry Yemanov [ dimitr ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

SF_ID: 929233 =>

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue is related to QA105 [ QA105 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10728 ] => Firebird [ 15103 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant