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
Hi! I'm trying to introduce jsonb into a project (see GreptimeTeam/greptimedb#4619), but the project relies on the non-preserve-order nature of serde_json, which conflicts with jsonb. I've noticed that the feature is used to preserve the order of json objects in conversions, while the order of objects is not guaranteed according to RFC. Are there other things relying on it?
I wonder if it's proper to put a trigger on the feature as what serde_json does for better compatibility. If so, I'd like to submit a patch for it :)
The text was updated successfully, but these errors were encountered:
Hi! I'm trying to introduce
jsonb
into a project (see GreptimeTeam/greptimedb#4619), but the project relies on the non-preserve-order nature ofserde_json
, which conflicts withjsonb
. I've noticed that the feature is used to preserve the order of json objects in conversions, while the order of objects is not guaranteed according to RFC. Are there other things relying on it?I wonder if it's proper to put a trigger on the feature as what
serde_json
does for better compatibility. If so, I'd like to submit a patch for it :)The text was updated successfully, but these errors were encountered: