#25133: Changing a PositiveIntegerField to an IntegerField does not remove >=0
check in migration
-------------------------------------+-------------------------------------
Reporter: jproffitt | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Normal | Resolution: needsinfo
Keywords: migrations, | Triage Stage:
postgres | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
I never knew this option even existed, I assumed you were setting a
`search_path` on [https://docs.djangoproject.com/en/1.8/ref/signals
/#connection-created connection_created].
After
[https://github.com/django/django/blob/a51070e7434426467869147608c5a8ca58e21e00/django/db/backends/postgresql/introspection.py#L139-L163
verification] It looks like were really just retrieving constraints
defined in the `public` schema.
--
Ticket URL: <https://code.djangoproject.com/ticket/25133#comment:7>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.2da479b70e6ac4a7ef02bb386c8edefa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
