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
When using a custom decoder module with a nullable column such as @Settings?{settings} and querying the rows with get_many, I see the decoder getting called with an empty string instead of a null. I'm using the postgres driver against cockroachdb. Not sure what layer this could be going wrong at yet - the postgres driver providing a string instead of null or caqti parsing it wrong, so I wanted to verify that this the use case of custom types and optionals is supported by the ppx first. I see the following error when running a select statement:
Failed handling request Caqti_type.Reject("Line 1, bytes -1-0:\nUnexpected end of input")
The text was updated successfully, but these errors were encountered:
When using a custom decoder module with a nullable column such as
@Settings?{settings}
and querying the rows with get_many, I see the decoder getting called with an empty string instead of a null. I'm using the postgres driver against cockroachdb. Not sure what layer this could be going wrong at yet - the postgres driver providing a string instead of null or caqti parsing it wrong, so I wanted to verify that this the use case of custom types and optionals is supported by the ppx first. I see the following error when running a select statement:The text was updated successfully, but these errors were encountered: