#22260: Custom model field: field.db_type not called for (initial) migration /
docs
wrong? (DurationField)
----------------------------+--------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by Marc Tamlyn <marc.tamlyn@…>):
* resolution: duplicate => fixed
Comment:
In [changeset:"d22b291890c1736a40c0ad97448c7318df2eebb2"]:
{{{
#!CommitTicketReference repository=""
revision="d22b291890c1736a40c0ad97448c7318df2eebb2"
Fixed #22001 -- Ensure db_type is respected.
db_parameters should respect an already existing db_type method and
return that as its type string. In particular, this was causing some
fields from gis to not be generated.
Thanks to @bigsassy and @blueyed for their work on the patch.
Also fixed #22260
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22260#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.e92fdadb1812e1f39c6decf95548bc6d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
