Skip to content
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.

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

Handle FK definitions w/o key references #1210

Merged
merged 1 commit into from Feb 23, 2024
Merged

Conversation

jberkel
Copy link
Collaborator

@jberkel jberkel commented May 27, 2023

Closes #1199

Copy link
Collaborator

@nathanfallet nathanfallet left a comment

Choose a reason for hiding this comment

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

LGTM. Test passes so it should fix the issue.

@@ -107,7 +107,7 @@ public struct ColumnDefinition: Equatable {
public struct ForeignKey: Equatable {
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't want to sidetrack this. But maybe while you are at it...

The ForeignKey struct is public, but its fields are not. Should they be public as well (given that the fields of ColumnDefinition itself are all are public)?

Copy link
Collaborator Author

@jberkel jberkel May 29, 2023

Choose a reason for hiding this comment

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

yes, quite a few more schema related fields are internal. I don't remember now if this was deliberate, but it looks like they should all be exposed.

@nathanfallet nathanfallet merged commit fd14c44 into master Feb 23, 2024
4 checks passed
@nathanfallet nathanfallet deleted the fix-null-fk-column branch February 23, 2024 13:51
@nathanfallet
Copy link
Collaborator

Please open a new PR if you want to make fields public.

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.

Fatal error: 'try!' expression unexpectedly raised an error: Unexpected null value for column "to"
3 participants