Making JSONField a core field was discussed in 
https://groups.google.com/d/topic/django-developers/sAgYOqBUvgI/discussion

Adam said, "my recent completion of its *JSONField* for MySQL 5.7+ is very 
similar to the *contrib.postgres* one, copying and adapting large parts of 
code from Marc Tamlyn's work. We all know how much everyone loves JSON 
these days. If anything, this could be a core field rather than a *contrib* one 
- Oracle and SQLite also have JSON capabilities now. JSON everywhere!"

Marc said, "I'm happy for JSONField to be made a core field on the 
condition that it's underlying support is more than a text blob on all our 
main databases. It sounds like this will soon be the case."

On Thursday, June 23, 2016 at 8:43:33 AM UTC-4, tedjohanss...@gmail.com 
wrote:
>
> 1 up on this one, would be really useful for me as well!
>
> On Thursday, 23 June 2016 10:57:07 UTC+1, Raphael Hertzog wrote:
>>
>> Hello, 
>>
>> in almost all projects I work on, I end up using a JSONField. Since 
>> I value being able to run with any database, I'm not relying on 
>> django.contrib.postgres.fields.JSONField. So I have been using 
>> pypi's django-jsonfield maintained by Matthew Schinckel: 
>> https://bitbucket.org/schinckel/django-jsonfield 
>> (I have also packaged this for Debian) 
>>
>> I have recently discovered pypi's "jsonfield" maintained by Brad Jasper: 
>> https://github.com/bradjasper/django-jsonfield 
>>
>> Both projects are very similar (and use the same python package name) and 
>> both projects are actually looking for a new maintainer... since I rely 
>> on 
>> something like this, I would be willing to try to merge the best of both 
>> modules into a possible django.contrib.jsonfield or directly into the 
>> core. 
>>
>> We could use this opportunity to let the newly-integrated field use 
>> DjangoJSONEncoder by default (see recent discussion about this) and 
>> django.contrib.postgres could register its additionals lookups into the 
>> generic field (assuming we use "jsonb" as underlying type for 
>> postgresql). 
>>
>> What do you think of this? 
>>
>> If inclusion into Django is not desired, then maybe we could aim to 
>> at least merge both of those projects in a single "blessed" third-party 
>> module that could be maintained in 
>> https://github.com/django/django-jsonfield? 
>>
>> Cheers, 
>> -- 
>> Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer 
>>
>> Discover the Debian Administrator's Handbook: 
>> → http://debian-handbook.info/get/ 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/889b5dba-d657-4b34-a878-028033956901%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to