Changes between Initial Version and Version 1 of Ticket #30476


Ignore:
Timestamp:
May 14, 2019, 6:01:49 AM (6 years ago)
Author:
Héctor Pablos
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #30476 – Description

    initial v1  
    1 Right now, the {{{inspectdb}}} command, when the {{{django.contrib.postgres}}} app is added to {{{INSTALLED_APPS}}} in the settings, is able to detect {{{jsonb}}} fields and generate a model with the right {{{django.contrib.postgres.fields.JSONField}}}, but that's not the case for simple {{json}} fields.
     1Right now, the {{{inspectdb}}} command, when the {{{django.contrib.postgres}}} app is added to {{{INSTALLED_APPS}}} in the settings, is able to detect {{{jsonb}}} fields and generate a model with the right {{{django.contrib.postgres.fields.JSONField}}}, but that's not the case for simple {{{json}}} fields.
    22
    33[https://docs.djangoproject.com/en/2.2/ref/contrib/postgres/fields/#django.contrib.postgres.fields.JSONField The documentation] states that the {{{JSONField}}} uses internally a PostgreSQL {{{jsonb}}} field, but I wonder if normal {{{json}}} fields could also be detected as a {{{JSONField}}}, as they can perfectly work for unmanaged models.
Back to Top