-
Notifications
You must be signed in to change notification settings - Fork 85
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
Fix #3154 #3263
Fix #3154 #3263
Conversation
|
||
~ConnectionQueryAsyncWorker() override = default; | ||
|
||
inline void Execute() override { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
compiler will inline automatically if the implementation write in header. So no need to mark inline
, same for other functions in this file.
py::gil_scoped_release release; | ||
auto queryResult = conn->query(statement); | ||
py::gil_scoped_acquire acquire; | ||
if (!queryResult->isSuccess()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would refactor l60-l65 with l72-l77 into a static function in this cpp file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if you wanna do the same on NodeJS side. I'll let u decide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I refactored it for Python. In Node.js I think I'll just keep the two workers as different classes for simplicity instead of creating a common base class.
b73d2f8
to
1583ea2
Compare
No description provided.