postgresql - ignore cross-schema FKs #1313
Merged
Conversation
This file contains 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
Signed-off-by: Caleb Lloyd <caleblloyd@gmail.com>
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.
I've been using SQLBoiler for a few months and it has been working very well!
Recently I added another schema to my database with cross-schema FKs. Some of the table names referenced in the FKs are the same in each schema.
SQLBoiler is trying to make relationships for these cross-schema FKs. But since SQLBoiler doesn't generate cross-schema models, so it shouldn't consider cross-schema FKs.
This is a fairly simple fix that checks the destination column's table
dstlookupname.relnamespaceand makes sure it matches thepg_namespace.oid