Hopefully this will soon be added to django core - it's one of the goals as part of Marc Tamlyn's kickstarter to improve postgres support in django.<p><a href="https://www.kickstarter.com/projects/mjtamlyn/improved-postgresql-support-in-django" rel="nofollow">https://www.kickstarter.com/projects/mjtamlyn/improved-postg...</a>
Really not trying to troll here, but I want to know why anyone uses a Python ORM here other than SQLAlchemy? It's been a while since I used Django's ORM but I recall the comparison between the two being very heavily in sqla's favor.
Have you looked at <a href="https://pypi.python.org/pypi/django-jsonfield/" rel="nofollow">https://pypi.python.org/pypi/django-jsonfield/</a> before building your json field? If so, can you elaborate about how those implementations compare with each other?
It's not Django, but I've built something quite similar for Rails, and have really loved using it. The combination of RDBMS stability and the flexibility of schemaless content is really powerful -- it is (IMHO) the best of both worlds.<p>Would love to hear people's experience with this kind of setup (no matter what software you're using)...I think it's a very interesting, and useful, direction to go, especially for new projects where you may not want the overhead of multiple storage systems.<p><a href="https://github.com/ageweke/flex_columns" rel="nofollow">https://github.com/ageweke/flex_columns</a>
Thanks for this! I use some of the various json fields that exist already but have been feeling like it is about time to start using the built in Postgres JSON support instead of just TextFields.
Remember to add it here when it's released: <a href="https://www.djangopackages.com/grids/g/json-fields/" rel="nofollow">https://www.djangopackages.com/grids/g/json-fields/</a>
What are the engineering trade-offs here? Metric were migrating from CouchDB, so using a JSON field is the obvious solution, but what about for new projects?<p>Compare it to say, Django-CMS, which achieves pretty much the same thing by storing the tree data-structure directly in SQL. The `django-mptt` library handles the details of efficiently implementing a tree structure in SQL, and `south` simplifies database scheme migration. As a programmer, which system would you rather work with?
You should use hstore to store json in postgres also - no?<p><a href="https://github.com/djangonauts/django-hstore" rel="nofollow">https://github.com/djangonauts/django-hstore</a><p>I think the issue with that is it converts everything to string so you need to use json.loads().