#36129: Geodjango migrations ignore change of dimension in MultiPointField
------------------------------+--------------------------------------
Reporter: Paweł Kotiuk | Owner: (none)
Type: Bug | Status: closed
Component: GIS | Version: dev
Severity: Normal | Resolution: invalid
Keywords: migrations | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by Paweł Kotiuk):
> find more specific information detailing that Django is at fault in this
specific case, specifically once you remove the potentially incorrect
default in place.
This problem also exists when there is no default.
You can try to reproduce with simplified model without default (and
simpler tests)
{{{#!div style="font-size: 80%"
model
{{{#!python
class MultiPointTester(models.Model):
multipoint = models.MultiPointField(
dim=3,
blank=True,
null=True,
)
}}}
}}}
{{{#!div style="font-size: 80%"
test
{{{#!python
class MultipointTest(TransactionTestCase):
def test_multipoint_creation(self):
instance = models.MultiPointTester()
instance.save()
def test_always_working(self):
self.assertEqual(1, 1)
}}}
}}}
Migration from 3 to 2 still breaks every test (even `test_always_working`)
--
Ticket URL: <https://code.djangoproject.com/ticket/36129#comment:4>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194982f7212-31caec66-5fd1-48e1-9998-5e9936b2b65e-000000%40eu-central-1.amazonses.com.
