Changes between Version 97 and Version 98 of GeoDjango

Timestamp:

Oct 8, 2007, 1:25:25 PM (17 years ago)

Author:

jbronn

Comment:

updated w/new syntax

GeoDjango

@@ -4 +4 @@
 The [http://code.djangoproject.com/browser/django/branches/gis GIS] branch intends to be a world-class geographic web framework.  Our goal is to make it as easy as possible to build GIS web applications and harness the power of spatially enabled data.
 
-''News:'' The project has been [http://www.foss4g2007.org/presentations/view.php?abstract_id=222 accepted] to [http://www.foss4g2007.org/ FOSS4G 2007], thanks for your support!
-
-If you're working on the '''Django Sprint 2007''', there's a list of [http://code.djangoproject.com/wiki/SprintIdeas#GeoDjango GeoDjango-related priority tasks here].
+''News:'' The project was [http://www.foss4g2007.org/presentations/view.php?abstract_id=222 presented] at [http://www.foss4g2007.org/ FOSS4G 2007] on September 25, 2007. Thanks again for your support!
 
 '''Note:''' The documentation has been re-factored into several pages.  See the table of contents on the right for a complete listing of topics. Other !GeoDjango pages include:
@@ -46 +44 @@
      * The [source:django/branches/gis/django/contrib/gis/utils/LayerMapping.py LayerMapping] class will import vector data from GDAL-supported data sources.  This is still 'beta', and requires installation of the [wiki:GeoDjango#GDAL GDAL library].
    * As of r5657, "Lazy-Geometry" support was added (courtesy of Robert Coup's excellent patch in #4322) -- deprecating most of the  [wiki:GeoDjangoDatabaseAPI#ExtraInstanceMethods extra instance methods].
+   * As of of r6497, the `GeoMixin` was completely deprecated.
 
 === Phase 3 ===
  * Support additional spatial databases, in the following order of priority.
+   * Oracle Spatial (spatial support is included in Oracle's Express Edition)
    * DB2
      * When IBM DB2 Python DB-API adapter is available, work will commence on a spatial backend for DB2 [http://www-306.ibm.com/software/data/spatial/db2spatial/ Spatial Extender] add-on. ''See'' Antonio Cagiano, [http://antoniocangiano.com/2007/09/04/python-django-and-db2-status-update/ Python, Django and DB2 Status Update] blog posting.  
-   * Oracle Spatial (but only if I (jbronn) have access to a valid license)
    * MySQL
      * MySQL is last because its spatial offerings are not compliant with either the OGC and SQL/MM specifications.  Specifically, all operations are limited to the bounding boxes of the geometries.
@@ -106 +105 @@
 from django.contrib.gis.db import models
 
-class District(models.Model, models.GeoMixin):
+class District(models.Model):
     name = models.CharField(maxlength=35)
     num  = models.IntegerField()
@@ -113 +112 @@
     objects = models.GeoManager()
 
-class School(models.Model, models.GeoMixin):
+class School(models.Model):
     name  = models.CharField(maxlength=35)
     point = models.PointField()
@@ -120 +119 @@
 }}}
 
-'''Notes''':  The {{{GeoMixin}}} class allows for [wiki:GeoDjangoDatabaseAPI#ExtraInstanceMethods extra instance methods].  By default, a GiST index will be created for the School {{{PointField}}}s fields.  This behavior can be turned off by using {{{models.PointField(index=False)}}}. 
+'''Notes''':  The {{{GeoMixin}}} syntax is no longer needed as of r6467.  By default, a GiST index will be created for the School {{{PointField}}}s fields.  This behavior can be turned off by using {{{models.PointField(index=False)}}}. 
 
 === Using syncdb ===