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.

Sign up for GitHub

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

Jump to bottom

KILL Statements are giving exception when there is 0 row returned. #58

Closed
ahmeturun opened this issue Dec 22, 2020 · 2 comments
Closed

KILL Statements are giving exception when there is 0 row returned. #58

ahmeturun opened this issue Dec 22, 2020 · 2 comments
Assignees
@DarkWanderer

Comments

@ahmeturun
Copy link

ahmeturun commented Dec 22, 2020 •
edited
Loading

Using 'KILL QUERY' statement and trying to read the results gives error when the result returns 0 row. pls check the example I attached.
clickhouse-session-locked.zip
@DarkWanderer DarkWanderer self-assigned this Dec 23, 2020
@DarkWanderer
Copy link
Owner

Hi. You need to use ExecuteStatement rather than ExecuteReader/ExecuteQuery for DDL and 'administrative' statements (KILL/OPTIMIZE/ALTER/CREATE/DROP etc.) - the fact that they do return something sometimes is more of an exception than a rule. However, it still should not throw, I'll look into it.

DarkWanderer added a commit that referenced this issue Jan 16, 2021
@DarkWanderer
DataReader: do not throw exception on empty dataset #58
6675910
@DarkWanderer
Copy link
Owner

Will be released in next patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DarkWanderer DarkWanderer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DarkWanderer @ahmeturun