Fix to work in parallel with django.contrib.postgres.JSONField

[adamchainz]

See https://bitbucket.org/schinckel/django-jsonfield/issues/57/cannot-use-in-the-same-project-as-djangos

This issue looks complicated, there's a whole library by @kbussell to introduce that compatibility, https://github.com/kbussell/django-jsonfield-compat . The technique it uses should probably be merged in here!

[jakeatallyo]

What is the status of this bug? When can we expect a solution?

[adamchainz]

This is not being worked on. Please look into it yourself if it is important to you.

On Fri, 31 May 2019 at 23:39, Jake Urban ***@***.***> wrote: What is the status of this bug? When can we expect a solution? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5?email_source=notifications&email_token=AAGRMCNCWEZJRGJUASNH3QLPYGLIFA5CNFSM4G67AKUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWN6AQ#issuecomment-497868546>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGRMCNOBWV6MFDB4CMUGG3PYGLIFANCNFSM4G67AKUA> .

-- Adam

[laymonage]

I believe it's because of this line https://github.com/adamchainz/django-jsonfield/blob/master/jsonfield/fields.py#L198

The registration is shared on the same database connection (see https://github.com/psycopg/psycopg2/blob/master/lib/_json.py#L93), so it'll interfere with contrib.postgres.

A fix I'd propose is to use select_format. I'm using it in my draft of JSONField for Django here: https://github.com/django/django/blob/f5674d94b2ce0447158d63e61ea011b235744446/django/db/models/fields/json.py#L76.

Might worth a look if @jakeatallyo (or anyone else) is looking for a quick fix.

[adamchainz]

@laymonage thank you for that comment. If you have some spare time it would be great if you could create a PR for that fix and test it alongside current and future Django JSONFields. You are the world expert now :)