> Because some people can't stand having to work with SQL,migrations,schema and constraints, it's as simple as that
So use an ORM that understands Postgres' JSON columns. Don't need to write a single SQL statement, automagic migrations, no explicit schema (unless you make one), no constraints (unless you add them).
It works great, we did a rather large project last year using Django's ORM and postgres where we didn't know the final data schema until months after launch.
So use an ORM that understands Postgres' JSON columns. Don't need to write a single SQL statement, automagic migrations, no explicit schema (unless you make one), no constraints (unless you add them).
It works great, we did a rather large project last year using Django's ORM and postgres where we didn't know the final data schema until months after launch.