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
I'm curious how feasible it is to have the typescript response types accurately reflect the correct types based on the order of .selectAll('table') statements.
the pet fields take priority in the output, which makes person_id possibly null given the fact that we are performing a left join
However, the generated response type says person_id is not nullable. if you reverse the order, the expected outcome of person_id being non-nullable is accurate as the `person.person_id field will always be present
I'm curious how feasible it is to have the typescript response types accurately reflect the correct types based on the order of
.selectAll('table')
statements.For example:
Because this generates
the pet fields take priority in the output, which makes
person_id
possibly null given the fact that we are performing a left joinHowever, the generated response type says
person_id
is not nullable. if you reverse the order, the expected outcome ofperson_id
being non-nullable is accurate as the `person.person_id field will always be presentUpdated Playground with same name
person_id
columnsThe text was updated successfully, but these errors were encountered: