Re:Mongo but on Postgres and with strong consistency benefits
by cruffle_duffle on Monday July 08, 2024 @01:14PM
(#40907233)
A use case for me is I’m calling a lot of different 3rd party APIs that return similar things but in widely different data structures with a lot of information specific to that site. I take what is standard across all the API’s and store that in my relational database but anything I didn’t use I store in a JSONB field just in case I need it some time in the future.
In other words I’m not really using anything in that JSONB field… at least right now.
In other words I’m not really using anything in that JSONB field… at least right now.