From 075f13e44f203ee04f0c3abffc7d7a86c672cfe8 Mon Sep 17 00:00:00 2001
From: Sergey Fedoseev <fedoseev.sergey@gmail.com>
Date: Thu, 23 Mar 2017 22:07:50 +0500
Subject: [PATCH] Refs #27556, #27488 -- Updated support backends docs for
 isvalid lookup.

---
 docs/ref/contrib/gis/geoquerysets.txt | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/docs/ref/contrib/gis/geoquerysets.txt b/docs/ref/contrib/gis/geoquerysets.txt
index 8ca79b2ad0..d7135a7c39 100644
--- a/docs/ref/contrib/gis/geoquerysets.txt
+++ b/docs/ref/contrib/gis/geoquerysets.txt
@@ -306,7 +306,8 @@ SpatiaLite  ``Intersects(poly, geom)``
 ``isvalid``
 -----------
 
-*Availability*: `PostGIS <https://postgis.net/docs/ST_IsValid.html>`__
+*Availability*: `PostGIS <https://postgis.net/docs/ST_IsValid.html>`__,
+Oracle, SpatiaLite
 
 Tests if the geometry is valid.
 
@@ -314,9 +315,16 @@ Example::
 
     Zipcode.objects.filter(poly__isvalid=True)
 
-PostGIS equivalent::
+===================  ================================================================
+Backend              SQL Equivalent
+===================  ================================================================
+PostGIS, SpatiaLite  ``ST_IsValid(poly)``
+Oracle               ``SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(poly, 0.05) = 'TRUE'``
+===================  ================================================================
 
-    SELECT ... WHERE ST_IsValid(poly)
+.. versionchanged:: 1.11
+
+    Oracle and SpatiaLite support was added.
 
 .. fieldlookup:: overlaps