Add support for Postgres sqlbody functions#131
Merged
DanCardin merged 7 commits intoDanCardin:mainfrom Nov 13, 2025
Merged
Conversation
…ion if present when postgres version >= 14.0
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #131 +/- ##
==========================================
- Coverage 89.81% 89.79% -0.03%
==========================================
Files 86 86
Lines 4065 4096 +31
Branches 843 850 +7
==========================================
+ Hits 3651 3678 +27
- Misses 336 338 +2
- Partials 78 80 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
This PR extends the Postgres dialect functions and procedures to allow sqlbody functions introduced in Postgres 14.
My goal was to add this support without introducing an update to the Function or Procedure class APIs. Instead, I just needed to change the create statement construction if the language was
sqland definition was structured as a sqlbody, starting withBEGIN ATOMICfor procedures and functions orRETURNfor functions.On the database reflection side, I introduced version specific queries to get the sqlbody source but kept the existing structure of the returns.