Allow alternate languages and behaviors in the create_function SQL helper#1136
Merged
Allow alternate languages and behaviors in the create_function SQL helper#1136
Conversation
…e alternate language. Fixes #1120
happy dance |
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
2 participants
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 #1120
Previously it was always assumed you would be using Postgres, so the function would always be setup using
plpgsql. That's still default, but now you can specify justsqlif you want. However, it turns out that when usingsqlyou can't have aBEGIN END, so I had to remove those. We also used to just use the defaultVOLATILEbehavior, but if you needed to specifyIMMUTABLEthen you couldn't, but now you can.