enable to customize SQL comment prefix #20
Closed
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
sebdiem
force-pushed
the
sdr/cid_prefix_setting
branch
from
e15a5a6
to
f638a7b
Compare
In our use case, it would be very handy to be able to have the SQL comments formatted as correlation_id=XXX correlation_id=YYY (we may have more than one cid for the same request). We are using Splunk and this would provide auto-indexing for the correlation_id field.
sebdiem
force-pushed
the
sdr/cid_prefix_setting
branch
from
f638a7b
to
47ba425
Compare
|
reopened in #25 |
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.
In our use case, it would be very handy to be able to have the SQL
comments formatted as correlation_id=XXX.
We are using Splunk and this would provide auto-indexing for the
correlation_id field.