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

fix(types): forward relationships not found #565

Merged
merged 2 commits into from
Oct 28, 2024

Conversation

avallete
Copy link
Member

What kind of change does this PR introduce?

After investigating: supabase/supabase-js#943 (comment)
And looking at postgrest documentation I discovered the case where the embedding is referring to the destination of a "join table" for Many-To-Many relationships.

This is a try to handle it with the new select-query-parser. The solution is not perfect tough, since it doesn't check like PostgREST would at runtime "check that it's part of a composite key on the table". But I don't see how to do this without additional metadata from introspection. I'm open to suggestions here.

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@avallete avallete requested a review from soedirgo October 23, 2024 22:21
@avallete avallete merged commit ad1c533 into rc Oct 28, 2024
1 check passed
@soedirgo soedirgo deleted the fix/forward-relationships-not-found branch October 28, 2024 10:26
Copy link

🎉 This PR is included in version 1.17.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants