> avoid using any non-JSON Postgres types
i'm not sure I follow - why would they avoid using non-JSON types?
more generally however: I don't have a lot of insight into the usage/feedback for this extension, but I can ask the team
i'm not sure I follow - why would they avoid using non-JSON types?
more generally however: I don't have a lot of insight into the usage/feedback for this extension, but I can ask the team
A much more complex example would be representing a numrange where you have to preserve two bounds and their respective inclusivity/exclusivity, in JSON.