Type Inference Issue: Missing | null on Relational Fields in Drizzle ORM
When querying a company and joining related customer data, the resulting inferred TypeScript type for the customer property does not allow for null even though no record may exist. Because of this, the type inference is overly strict. In many cases, customer can be null, especially with a left join or if the relation is optional.
Expected Behavior:
When using a relational query (e.g. with: { customer: { ... } }), the inferred TypeScript type should include | null (or | undefined) for the customer property if it is optional or if no matching record exists.
Actual Behavior:
The inferred type forces the customer property to always exist, which causes runtime errors in bussines code because of the types mismatch.
Expected Behavior:
When using a relational query (e.g. with: { customer: { ... } }), the inferred TypeScript type should include | null (or | undefined) for the customer property if it is optional or if no matching record exists.
Actual Behavior:
The inferred type forces the customer property to always exist, which causes runtime errors in bussines code because of the types mismatch.
