You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge?
Currently one has to manually add the schema when creating a join or give an empty one and call recompute_schema. It would be nice to have a try_new which handles schema creation as well as does maybe some sanity checking.
Describe the solution you'd like
Add try_new to Join (and to all other plans currently missing it).
Describe alternatives you've considered
N/A
Additional context
Quality of life
The text was updated successfully, but these errors were encountered:
Join output schema is very difficult topic, especially when using USING.
It might be there is no one size fits all answer, but some (well defined) answer may be packaged as try_new (or differently named method), as long as it's not enforced as the only blessed way to construct Join.
I see how recompute_schema may be useful in the case where it's a newly constructed Join and doesn't have good schema yet. Fixing schema at construction time would be better -- ie creating truth is better than creating falsehood and fixing it later. Especially that recompute_schema has its own problems (#14357).
Is your feature request related to a problem or challenge?
Currently one has to manually add the schema when creating a join or give an empty one and call
recompute_schema
. It would be nice to have atry_new
which handles schema creation as well as does maybe some sanity checking.Describe the solution you'd like
Add
try_new
toJoin
(and to all other plans currently missing it).Describe alternatives you've considered
N/A
Additional context
Quality of life
The text was updated successfully, but these errors were encountered: