-
Notifications
You must be signed in to change notification settings - Fork 14
feature: add noreturn
opt for some DML operations
#356
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
feature: add noreturn
opt for some DML operations
#356
Conversation
Receiving |
9887bc1
to
4b100cc
Compare
Done, PR description updated |
91c5357
to
dcba2f2
Compare
it was decided to return to the idea:
|
dcba2f2
to
dc75380
Compare
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.
Let's change performance test cases to use noreturn
dc75380
to
492c870
Compare
Added a separate performance test for
|
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.
Please, rebase on master to verify that dev_checks are fine
This patch introduces `noreturn` opt for DML operarions: `insert`, `insert_object`, `insert_many`, `insert_object_many`, `replace`, `replace_object`, `replace_many`, `insert_object_many`, `upsert`, `upsert_object`, `upsert_many`, `upsert_object_many`, `update`, `delete`. The opt allows to suppress returning successfully processed tuple(s). Closes #267
492c870
to
af0ce90
Compare
Done |
This patch introduces
noreturn
opt for DML operarions:insert
,insert_object
,insert_many
,insert_object_many
replace
,replace_object
,replace_many
,insert_object_many
upsert
,upsert_object
,upsert_many
,upsert_object_many
update
delete
The opt allows to suppress returning successfully processed tuple(s).
Closes #267