Christopher Prohm comments

Results 62 comments of


                                            Christopher Prohm

Optional values are not handled correctly in tracing

I released 0.11.7 with the fix and yanked 0.11.6

jiff

Great idea! I have also been toying with the idea of using jiff in my my other projects due to the complexities of the chrono API. Definitely something to look...

Surface error more clearly for `push_validity`

Thanks a lot for the report! The error messages are definitely something to improve. If you have a concrete example, it would be quite helpful, so I can directly include...

Surface error more clearly for `push_validity`

My current plan is to include the relevant fields (and potentially other metadata) in the error message, e.g., > Cannot push null for non-nullable array (field: "$.nested.field") Would this have...

Surface error more clearly for `push_validity`

Released with 0.12.0

Use human_readble = false throughout all serializers, deserializers

I assume you have some kind of chrono or jiff type somewhere, right? - Chrono always serializes its `DateTime` type as string ([source](https://docs.rs/chrono/latest/src/chrono/datetime/serde.rs.html#32-51)). - Jiff as well ([source](https://docs.rs/jiff/latest/src/jiff/timestamp.rs.html#2837)). - UUID...

Use human_readble = false throughout all serializers, deserializers

The inconsistency is not great. However the bigger issue for me here is that I don't know what the default should be.

Remove arrow2 in next breaking release (most likely 0.12)

Work started in #196