Repository navigation
Fix trigger return type casing. - #422
Open
CRISvsGAME wants to merge 1 commit into
Open
CRISvsGAME wants to merge 1 commit into
CRISvsGAME wants to merge 1 commit into
Conversation
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.
Fix formatting of
TRIGGERwhen used as a function return type.By default, pgFormatter uppercases SQL keywords and lowercases data types. However,
RETURNS TRIGGERwas formatted using keyword case even thoughtriggeris a PostgreSQL pseudo-type.The fix recognizes
TRIGGERas a type in theRETURNScontext and applies the configured type case without affecting keyword formatting elsewhere, such asCREATE TRIGGER.Regression coverage includes:
RETURNS triggertRiGgErwith--type-case 0CREATE TRIGGERValidation:
prove -Ilib t/*.t— 97 tests passedperl t/regress_test.pl— passed