Fixes #4136: apoc.load.jdbcUpdate doesn't work in apoc.periodic.repeat procedure #4152
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4136
Modified the issue procedure a little bit, since even without validation that doesn't work,
as the
yield rowis absent.Changed the
Mode.DBMStoMode.READ, to solve the issue., as with Mode.DBMS the apoc.periodic.repeat fails due to this validation, which checks that the inner procedures/queries have to be of type read or write.This should not be a breaking-change anyway,
since with this procedure, we cannot execute operations against the neo4j database, instead against the SQL database,
so the mode SCHEMA should not be needed.