Update materialize doc with simpler SQL #290
Merged
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 think a single
select
comes off as simpler to grok right now.The motivation here was that when I was grafting materialize onto an existing project for a demo, I found the ORM that project used made it much easier to build non-union queries.
My only concern with this example is that non-inner joins are much less common and might be confusing in their own right - might be worth coming back to this and expanding on the reason (in this case it's because we don't want to discard rows from the join if they don't have a
set_to_set
match, since they might have a "direct"member_to_set
match.)