Mark the test for left/right lookup types as a known failure on PostGIS 2.0.

This commit is contained in:
Justin Bronn 2012-10-09 17:20:51 -07:00
parent 32ac067a6d
commit f578ee32fa

View File

@ -11,7 +11,7 @@ from django.contrib.gis.tests.utils import (
no_mysql, no_oracle, no_spatialite, no_mysql, no_oracle, no_spatialite,
mysql, oracle, postgis, spatialite) mysql, oracle, postgis, spatialite)
from django.test import TestCase from django.test import TestCase
from django.utils import six from django.utils import six, unittest
from .models import Country, City, PennsylvaniaCity, State, Track from .models import Country, City, PennsylvaniaCity, State, Track
@ -295,6 +295,13 @@ class GeoLookupTest(TestCase):
self.assertEqual(2, len(qs)) self.assertEqual(2, len(qs))
for c in qs: self.assertEqual(True, c.name in cities) for c in qs: self.assertEqual(True, c.name in cities)
# The left/right lookup tests are known failures on PostGIS 2.0+
# until the following bug is fixed:
# http://trac.osgeo.org/postgis/ticket/2035
# TODO: Ensure fixed in 2.0.2, else modify upper bound for version here.
if (2, 0, 0) <= connection.ops.spatial_version <= (2, 0, 1):
test_left_right_lookups = unittest.expectedFailure(test_left_right_lookups)
def test_equals_lookups(self): def test_equals_lookups(self):
"Testing the 'same_as' and 'equals' lookup types." "Testing the 'same_as' and 'equals' lookup types."
pnt = fromstr('POINT (-95.363151 29.763374)', srid=4326) pnt = fromstr('POINT (-95.363151 29.763374)', srid=4326)