Raw sql nullable types, sql<Type | undefined>
This gets inferred to
SQL<any>Is there a way to have a nullable type when using raw sql?
Dyes, it should use the exact type passed as the generic
Dcould you post your whole query and the definition of
Type
VSorry, mistook the issue a bit, it seems that without the its inferred properly, but if its mapped then it is always non-nullable. Probably a niche situation but still a bit unusual, here's my whole thing
Type
But if I remove the
It correctly is inferred to
The is a custom PGColumn. But I don't think I can pass it to mapWith but rather I have to use a column from the table, this is a seperate question, don't think its related to the above problem
Type
But if I remove the
It correctly is inferred to
The is a custom PGColumn. But I don't think I can pass it to mapWith but rather I have to use a column from the table, this is a seperate question, don't think its related to the above problem
DOK I see - this is an edge case I didn't think about
We automatically assign the result type when you call based on the mapper return type
So the fastest fix on your side would be to make a custom mapper function that returns a nullable result, and pass it into
something like
We automatically assign the result type when you call based on the mapper return type
So the fastest fix on your side would be to make a custom mapper function that returns a nullable result, and pass it into
something like
VYeah quite a niche situation, glad I caught it. Thanks @Dan Kochetov
VWill you create an issue on GH if this warrants one? I would like to follow it
DYou can create it yourself if you'd like 
VGitHub
Describe want to want Description When using .mapWith(), nullable type inference is not being properly handled. Without the .mapWith(), the type is inferred correctly, but when it's mapped, the...