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
I'm inserting rows that have json that I have no control over, so I can get something like this:
{ "a" : { "b" : "c" } }
{ "a" : 100 }
{ "foo": "bar" }
where the "a" value can be another json element, an integer, or not even there. Like in issue #3 where the value is missing it is skipped over can items that cannot be cast to the correct response type be skipped over?
Currently I'm getting "ERROR: wrong json type found string, expected number" which is understandable, but there's no way I can avoid it.
The text was updated successfully, but these errors were encountered:
Yes, it is not possible to extract unknown data type without getting an error because in other case you can't distinguish null value from the "wrong" (unexpected) type. Possible solutions:
to add a bunch of functions that silently return null on unexpected type (not very elegant)
to add complex type introspection functions (it will require some pgsql code).
I'm inserting rows that have json that I have no control over, so I can get something like this:
{ "a" : { "b" : "c" } }
{ "a" : 100 }
{ "foo": "bar" }
where the "a" value can be another json element, an integer, or not even there. Like in issue #3 where the value is missing it is skipped over can items that cannot be cast to the correct response type be skipped over?
Currently I'm getting "ERROR: wrong json type found string, expected number" which is understandable, but there's no way I can avoid it.
The text was updated successfully, but these errors were encountered: