#31967: Resolving an output_field for mixed types crashes in database functions.
-------------------------------------+-------------------------------------
Reporter: Matt Hegarty | Owner: Hasan
| Ramezani
Type: Bug | Status: closed
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Anne "Anya" Macedo):
Replying to [comment:14 Simon Charette]:
> I suggest posting your question in the
[https://forum.djangoproject.com/c/internals/geodjango/13 GeoDjango
category of the forum] instead.
>
> I suspect you only have to pass
`output_field=models.MultiPolygonField()` when initializing your
`SimplifyPreserveTopology` as hinted by the error message: `You must set
output_field.`
>
> {{{#!python
> SimplifyPreserveTopology(
> F(geometry), 0.0439453125, output_field=models.MultiPolygonField()
> )
> }}}
I believe it worked! Been trying to fix this bug for a whole week :)
--
Ticket URL: <https://code.djangoproject.com/ticket/31967#comment:15>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ab7ccc181-b681a7d9-ab6f-4eb7-8182-b6ef7a84530d-000000%40eu-central-1.amazonses.com.
