Closed chris-martin closed 4 months ago
I don't think there should be issues. Have you tried this?
I haven't tried it, no. I don't have any particular reason to believe that it would be a problem, I just don't know how the underlying mechanism works, so it seemed vaguely reasonable that consumption of the entire row might have been an assumption the library has. About to yolo some stuff into production so I thought I'd just try asking for some reassurance :upside_down_face:
When defining a
Hasql.Decoders.Row
, is it mandatory for the row decoder to read every column in every row, or is row decoding allowed to halt early? For example, suppose the first column in the selected table is aBool
which, ifFalse
, means that we don't care about the rest of the row.Is this sort of row decoder okay, or is there some potential problem that may arise?