bug: fix query representation to string#290
Merged
lsabi merged 1 commit intorethinkdb:masterfrom Apr 27, 2023
Merged
Conversation
|
Code Climate has analyzed commit 99c521d and detected 0 issues on this pull request. View more on Code Climate. |
lsabi
approved these changes
Apr 27, 2023
Contributor
|
Thanks for the contribution! |
This file contains hidden or 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.
Reason for the change
If applicable, link the related issue/bug report or write down in few sentences the motivation.
Trying to build a query dynamically and log it
Description
Seems like there was a mass change from
sttostatementduring rethinkdb 2.1->2.4 but that specifically property was not converted right, thus, left the changed line defunc.This PR changes it back to
stuntil maintainer finishes the refactorCode examples
will yield an error of
Checklist