NullAwareTypeConverter not usable from drift files when the column is non-nullable about drift

[simolus3]

This would technically be unsound since you can override toSql in a NullAwareTypeConverter subclass to return null for non-null inputs.

But is there a reason for using null-aware type converters here? When applying a type converter not supporting null values to a nullable column, drift will actually wrap the converter in a NullAwareTypeConverter for you (and I think it should also do this for mapped non-nullable columns in outer joins which might then be null). So if the intention is to map null in Dart to NULL in SQL, the easiest way is to declare the converter with non-nullable types and let drift figure out the null handling on columns where that's necessary.

[kuhnroyal]

Hmm, I never tried it with a non-nullable converter....

[kuhnroyal]

Ok, this works for me, sorry for the noise.