> I much rather build upon the relative robustness and consistency of the sql I got so far, than JSON that is all over the place. Yup. > almost every time I m

> I much rather build upon the relative robustness and consistency of the sql I got so far, than JSON that is all over the place. Yup. > almost every time I made a JSON column in Postgres for the sake of saving time in the past, it slowed me down almost immediately after adding it Backs my experience fixing software from companies that had terrible data loss issues after these JSON hacks reared their ugly head. I am not saying JSON does not belong in a DB - I have many well tested and audited code that does do that. What I am saying is I have seen things go wrong far too much, for me to trust that someone who proposes that approach to actually know what they are getting themselves into. Plus, it's way cheaper to use a custom built KeyValDB that actually supports object semantics if one does not mean to use RDBMS semantics. Anyways, I am being severely downvoted and cant respond until a few hours between posts so I wont be responding any longer on this thread as I have a lot of work to do the next few days and cant wait around. See my other comments. Contact info in my profile, would love to be in touch!