Skip to content

fix (postgres): make foreign key discovery schema-specific #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
tyt2y3 merged 3 commits into from
Nov 15, 2025
Merged

fix (postgres): make foreign key discovery schema-specific #157

tyt2y3 merged 3 commits into from
Nov 15, 2025

Conversation

@qingyiwebt
Copy link
Contributor

@qingyiwebt qingyiwebt commented Nov 15, 2025

PR Info

  • Closes

New Features

Bug Fixes

  • Make foreign key discovery schema-specific when using PostgreSQL

Breaking Changes

Changes

  • Make foreign key discovery schema-specific when using PostgreSQL

tyt2y3
tyt2y3 approved these changes Nov 15, 2025
View reviewed changes
Copy link
Member

@tyt2y3 tyt2y3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you again

@tyt2y3 tyt2y3 merged commit f63179f into SeaQL:master Nov 15, 2025
25 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tyt2y3 tyt2y3 tyt2y3 approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Create duplicated foreign key (constraint) when using PostgreSQL

2 participants

@qingyiwebt @tyt2y3