Prune some log traces from examples #966
Merged
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.
The flag
--log trace
shows up in a lot of examples but for the most part doesn't fit the example and can even result in decreased performance as the database spends time logging everything. See surrealdb/surrealist#532 (comment)This removes them in places where verbosity is not the subject, and makes it clear in other parts that it is being added to make the output verbose so that the reader knows that
--log trace
is only there for that specific case and doesn't need to be there otherwise.Edit: Also replaces most of the remaining with --debug which is enough to demonstrate a more verbose output.