Skip to content

Account relation dependencies used by routines as composite types#268

Closed
joas8211 wants to merge 1 commit into
stripe:mainfrom
joas8211:proc-rel-deps
Closed

Account relation dependencies used by routines as composite types#268
joas8211 wants to merge 1 commit into
stripe:mainfrom
joas8211:proc-rel-deps

Conversation

@joas8211
Copy link
Copy Markdown

@joas8211 joas8211 commented Feb 9, 2026

Description

Functions and procedures can use tables and views as composite types for parameter and return types. Those dependencies must be accounted for to avoid out of order errors in diffs.

Resolves #248

Motivation

I'm building a project which uses table as function parameter type and couldn't get it working without these changes.

Testing

Test cases are still missing which is why this PR is marked as draft. I'll add tests soon. I'd be happy to take feedback even before writing tests.

Functions and procedures can use tables and views as composite types for
parameter and return types. Those dependencies must be accounted for.
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Feb 9, 2026

CLA assistant check
All committers have signed the CLA.

@joas8211
Copy link
Copy Markdown
Author

The fix didn't actually work for me. It's complaining about circular dependencies. I have a big schema already so debugging it is a chore. I'd be happy if someone else took this inspiration from this to resolve the issue. I'll close this PR because I don't have time to finish it currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Functions with knowable dependencies are created before the tables they depend on

1 participant