Curious though isn't it.  I guess having to specify this here implies that
someone is handcrafting a database query somewhere else in the code.  Seems
like it would have been better to mandate the model field name and use
db_column to associate it with whatever column name the backend requires.


On 22 January 2014 15:26, Mark Hepburn <notifications@github.com> wrote:

> In django_pyodbc_gis/models.py:
>
> > +    #
> > +    # This hack should be removed when the bug is fixed.
> > +    #
> > +    # https://docs.djangoproject.com/en/dev/ref/contrib/gis/measure/#supported-units
> > +    #
> > +    @property
> > +    def units(self):
> > +        num, name = super(SpatialRefSys, self).units
> > +        if name.lower() == 'decimal degree':
> > +            name = 'Decimal Degree'
> > +        else:
> > +            name = name.lower()
> > +        return (num, name)
> > +
> > +    #
> > +    # TODO: Is this important?  Am I doing it right?
>
> Yeah, that's the db column name
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/condense/django-pyodbc-gis/pull/1/files#r9064982>
> .
>