Re: [Django] #27056: changing dim property for gemotries does not generate correct migration

[Django]

#27056: changing dim property for gemotries does not generate correct migration
-+-
 Reporter:  billyburly   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango postgres   | Triage Stage:  Accepted
  postgis|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 I added a pull request to fix this on PostGIS:
 [https://github.com/django/django/pull/7264 PR].

 On Spatialite, things are currently a bit messy, for several different
 reasons. It's currently not possible to alter geometry fields on
 Spatialite. I would suggest to commit the PostGIS changes and to open
 another ticket specific to Spatialite (which might take longer to solve).

--
Ticket URL: 
Django 
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/068.5f002a63e7cc10dc4bc81c63165dbdd0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27056: changing dim property for gemotries does not generate correct migration

[Django]

#27056: changing dim property for gemotries does not generate correct migration
-+-
 Reporter:  billyburly   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  geodjango postgres   | Triage Stage:  Accepted
  postgis|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Migrations
 * needs_tests:   => 0
 * version:  1.9 => master
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


--
Ticket URL: 
Django 
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/068.f2740dd59d384b310a5795b6b75797b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27056: changing dim property for gemotries does not generate correct migration

[Django]

#27056: changing dim property for gemotries does not generate correct migration
---+
 Reporter:  billyburly |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:  geodjango postgres postgis
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Changing the dim property for a geometry field does not generate a
 migration that changes the number of dimensions a geometry in the DB has.

 Changing a field in a model from {{{models.LineStringField(null=True)}}}
 to {{{models.LineStringField(null=True, dim=3)}}} creates the following
 migration and sql:

 {{{
 # -*- coding: utf-8 -*-
 # Generated by Django 1.9.8 on 2016-08-12 15:28
 from __future__ import unicode_literals

 import django.contrib.gis.db.models.fields
 from django.db import migrations


 class Migration(migrations.Migration):

 dependencies = [
 ('rivermap', '0026_auto_20160624_1827'),
 ]

 operations = [
 migrations.AlterField(
 model_name='sectionextra',
 name='streamPath',
 field=django.contrib.gis.db.models.fields.LineStringField(dim=3,
 null=True, srid=4326),
 ),
 ]
 }}}
 {{{
 BEGIN;
 --
 -- Alter field streamPath on sectionextra
 --
 ALTER TABLE "rivermap_sectionextra" ALTER COLUMN "streamPath" TYPE
 geometry(LINESTRINGZ,4326) USING "streamPath"::geometry(LINESTRINGZ,4326);

 COMMIT;
 }}}
 This causes an exception during migration because PostGIS returned the
 following error
 {{{
 Column has Z dimension but geometry does not
 }}}

 According to http://gis.stackexchange.com/questions/109410/postgis-column-
 has-z-dimension-but-geometry-does-not the {{{ST_Force3D}}} function needs
 to be used for the USING clause.

--
Ticket URL: 
Django 
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/053.e971bed3d06cc89cc92aa5a03f0199d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.