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

Consume results of write-only transactions #176

Merged
merged 1 commit into from
Oct 21, 2022

Conversation

fbiville
Copy link
Contributor

While it's not strictly necessary, since the Neo4j server will execute the transaction queries just before commit at latest, consuming results makes sure the queries are run right when the client starts pulling results.

Another advantage is that some query errors will surface when you consume results and not when you commit.

While it's not strictly necessary, since the Neo4j server will
execute the transaction queries just before commit at latest,
consuming results makes sure the queries are run right when the
client starts pulling results.

Another advantage is that some query errors will surface when you
consume results and not when you commit.
Copy link
Contributor

@lumjjb lumjjb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @fbiville !

Copy link
Collaborator

@mihaimaruseac mihaimaruseac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTMs to me, thank you very much

@kodiakhq kodiakhq bot merged commit 03e2c33 into guacsec:main Oct 21, 2022
lumjjb pushed a commit that referenced this pull request Oct 21, 2022
While it's not strictly necessary, since the Neo4j server will
execute the transaction queries just before commit at latest,
consuming results makes sure the queries are run right when the
client starts pulling results.

Another advantage is that some query errors will surface when you
consume results and not when you commit.
@lumjjb
Copy link
Contributor

lumjjb commented Oct 21, 2022

hi @fbiville noticed that there was an issue with the sign off message (DCO), with your permission can we add the DCO sign off line on your behalf?

@fbiville fbiville deleted the result_consumption_fix branch March 7, 2023 17:05
@fbiville
Copy link
Contributor Author

fbiville commented Mar 7, 2023

@lumjjb I somehow completely missed your message, apologies. No problem to add the sign off as you've probably already done by now

mrizzi pushed a commit to mrizzi/guac that referenced this pull request Nov 25, 2024
…ec#176)

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Co-authored-by: red-hat-konflux[bot] <126015336+red-hat-konflux[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants