I originally opened an issue on crystal-db, though Brian pointed out a change here. I've read though the change, however, I'm still not clear how to update my code to accomodate the new strategy.
I'm upgrading from Crystal 1.5.0, crystal-db 0.10.0, crystal-pg 0.23.1 and I'm seeing this error:
In Postgres I have a function which RETURNS jsonb. JSON::Any worked fine for me before. I don't want to cast the JSON to a serializable class because the JSON is too verbose with nested data.
Any tips on what I need to change to keep the JSON::Any output? Or, is that a lost cause?
I originally opened an issue on crystal-db, though Brian pointed out a change here. I've read though the change, however, I'm still not clear how to update my code to accomodate the new strategy.
I'm upgrading from Crystal
1.5.0
, crystal-db0.10.0
, crystal-pg0.23.1
and I'm seeing this error:from:
In Postgres I have a function which
RETURNS jsonb
.JSON::Any
worked fine for me before. I don't want to cast the JSON to a serializable class because the JSON is too verbose with nested data.Any tips on what I need to change to keep the
JSON::Any
output? Or, is that a lost cause?