List:Commits« Previous MessageNext Message »
From:paul Date:April 10 2007 4:45pm
Subject:svn commit - mysqldoc@docsrva: r5804 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2007-04-10 18:45:53 +0200 (Tue, 10 Apr 2007)
New Revision: 5804

Log:
 r23077@polar:  paul | 2007-04-10 11:01:40 -0500
 Clarify meaning of some spatial functions.


Modified:
   trunk/refman-4.1/spatial-extensions.xml
   trunk/refman-5.0/spatial-extensions.xml
   trunk/refman-5.1/spatial-extensions.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:23076
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:18854
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:23077
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:18854
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593


Modified: trunk/refman-4.1/spatial-extensions.xml
===================================================================
--- trunk/refman-4.1/spatial-extensions.xml	2007-04-10 16:45:01 UTC (rev 5803)
+++ trunk/refman-4.1/spatial-extensions.xml	2007-04-10 16:45:53 UTC (rev 5804)
Changed blocks: 7, Lines Added: 37, Lines Deleted: 20; 4709 bytes

@@ -4325,6 +4325,8 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangle of <replaceable>g1</replaceable> contains the
             Minimum Bounding Rectangle of <replaceable>g2</replaceable>.
+            This tests the opposite relationship as
+            <literal>MBRWithin()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4430,7 +4432,11 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangles of the two geometries
             <replaceable>g1</replaceable> and
-            <replaceable>g2</replaceable> overlap.
+            <replaceable>g2</replaceable> overlap. The term
+            <emphasis>spatially overlaps</emphasis> is used if two
+            geometries intersect and their intersection results in a
+            geometry of the same dimension but not equal to either of
+            the given geometries.
           </para>
 
           <remark role="help-description-end"/>

@@ -4453,7 +4459,11 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangles of the two geometries
             <replaceable>g1</replaceable> and
-            <replaceable>g2</replaceable> touch.
+            <replaceable>g2</replaceable> touch. Two geometries
+            <emphasis>spatially touch</emphasis> if the interiors of the
+            geometries do not intersect, but the boundary of one of the
+            geometries intersects either the boundary or the interior of
+            the other.
           </para>
 
           <remark role="help-description-end"/>

@@ -4476,6 +4486,8 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangle of <replaceable>g1</replaceable> is within the
             Minimum Bounding Rectangle of <replaceable>g2</replaceable>.
+            This tests the opposite relationship as
+            <literal>MBRWithin()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4509,26 +4521,29 @@
       </para>
 
       <para>
-        Currently, MySQL does not implement these functions according to
-        the specification. Those that are implemented return the same
-        result as the corresponding MBR-based functions. This includes
-        functions in the following list other than
-        <literal>Distance()</literal> and <literal>Related()</literal>.
+        The return values 1 and 0 indicate true and false, respectively.
       </para>
 
-      <remark role="note">
-        Crosses() is an exception here: It exists but MBRCrosses() does
-        not.
-      </remark>
+      <note>
+        <para>
+          Currently, MySQL does not implement these functions according
+          to the specification. Those that are implemented return the
+          same result as the corresponding MBR-based functions. This
+          includes functions in the following list other than
+          <literal>Distance()</literal> and
+          <literal>Related()</literal>.
+        </para>
 
-      <para>
-        These functions may be implemented in future releases with full
-        support for spatial analysis, not just MBR-based support.
-      </para>
+        <remark role="note">
+          Crosses() is an exception here: It exists but MBRCrosses()
+          does not.
+        </remark>
 
-      <para>
-        The return values 1 and 0 indicate true and false, respectively.
-      </para>
+        <para>
+          These functions may be implemented in future releases with
+          full support for spatial analysis, not just MBR-based support.
+        </para>
+      </note>
 
       <remark role="help-category" condition="Geometry relations@Geographic Features"/>
 

@@ -4550,7 +4565,8 @@
           <para>
             Returns 1 or 0 to indicate whether
             <replaceable>g1</replaceable> completely contains
-            <replaceable>g2</replaceable>.
+            <replaceable>g2</replaceable>. This tests the opposite
+            relationship as <literal>Within()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4791,7 +4807,8 @@
           <para>
             Returns 1 or 0 to indicate whether
             <replaceable>g1</replaceable> is spatially within
-            <replaceable>g2</replaceable>.
+            <replaceable>g2</replaceable>. This tests the opposite
+            relationship as <literal>Contains()</literal>.
           </para>
 
           <remark role="help-description-end"/>


Modified: trunk/refman-5.0/spatial-extensions.xml
===================================================================
--- trunk/refman-5.0/spatial-extensions.xml	2007-04-10 16:45:01 UTC (rev 5803)
+++ trunk/refman-5.0/spatial-extensions.xml	2007-04-10 16:45:53 UTC (rev 5804)
Changed blocks: 7, Lines Added: 37, Lines Deleted: 20; 4709 bytes

@@ -4341,6 +4341,8 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangle of <replaceable>g1</replaceable> contains the
             Minimum Bounding Rectangle of <replaceable>g2</replaceable>.
+            This tests the opposite relationship as
+            <literal>MBRWithin()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4446,7 +4448,11 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangles of the two geometries
             <replaceable>g1</replaceable> and
-            <replaceable>g2</replaceable> overlap.
+            <replaceable>g2</replaceable> overlap. The term
+            <emphasis>spatially overlaps</emphasis> is used if two
+            geometries intersect and their intersection results in a
+            geometry of the same dimension but not equal to either of
+            the given geometries.
           </para>
 
           <remark role="help-description-end"/>

@@ -4469,7 +4475,11 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangles of the two geometries
             <replaceable>g1</replaceable> and
-            <replaceable>g2</replaceable> touch.
+            <replaceable>g2</replaceable> touch. Two geometries
+            <emphasis>spatially touch</emphasis> if the interiors of the
+            geometries do not intersect, but the boundary of one of the
+            geometries intersects either the boundary or the interior of
+            the other.
           </para>
 
           <remark role="help-description-end"/>

@@ -4492,6 +4502,8 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangle of <replaceable>g1</replaceable> is within the
             Minimum Bounding Rectangle of <replaceable>g2</replaceable>.
+            This tests the opposite relationship as
+            <literal>MBRWithin()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4525,26 +4537,29 @@
       </para>
 
       <para>
-        Currently, MySQL does not implement these functions according to
-        the specification. Those that are implemented return the same
-        result as the corresponding MBR-based functions. This includes
-        functions in the following list other than
-        <literal>Distance()</literal> and <literal>Related()</literal>.
+        The return values 1 and 0 indicate true and false, respectively.
       </para>
 
-      <remark role="note">
-        Crosses() is an exception here: It exists but MBRCrosses() does
-        not.
-      </remark>
+      <note>
+        <para>
+          Currently, MySQL does not implement these functions according
+          to the specification. Those that are implemented return the
+          same result as the corresponding MBR-based functions. This
+          includes functions in the following list other than
+          <literal>Distance()</literal> and
+          <literal>Related()</literal>.
+        </para>
 
-      <para>
-        These functions may be implemented in future releases with full
-        support for spatial analysis, not just MBR-based support.
-      </para>
+        <remark role="note">
+          Crosses() is an exception here: It exists but MBRCrosses()
+          does not.
+        </remark>
 
-      <para>
-        The return values 1 and 0 indicate true and false, respectively.
-      </para>
+        <para>
+          These functions may be implemented in future releases with
+          full support for spatial analysis, not just MBR-based support.
+        </para>
+      </note>
 
       <remark role="help-category" condition="Geometry relations@Geographic Features"/>
 

@@ -4566,7 +4581,8 @@
           <para>
             Returns 1 or 0 to indicate whether
             <replaceable>g1</replaceable> completely contains
-            <replaceable>g2</replaceable>.
+            <replaceable>g2</replaceable>. This tests the opposite
+            relationship as <literal>Within()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4807,7 +4823,8 @@
           <para>
             Returns 1 or 0 to indicate whether
             <replaceable>g1</replaceable> is spatially within
-            <replaceable>g2</replaceable>.
+            <replaceable>g2</replaceable>. This tests the opposite
+            relationship as <literal>Contains()</literal>.
           </para>
 
           <remark role="help-description-end"/>


Modified: trunk/refman-5.1/spatial-extensions.xml
===================================================================
--- trunk/refman-5.1/spatial-extensions.xml	2007-04-10 16:45:01 UTC (rev 5803)
+++ trunk/refman-5.1/spatial-extensions.xml	2007-04-10 16:45:53 UTC (rev 5804)
Changed blocks: 7, Lines Added: 37, Lines Deleted: 20; 4709 bytes

@@ -4337,6 +4337,8 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangle of <replaceable>g1</replaceable> contains the
             Minimum Bounding Rectangle of <replaceable>g2</replaceable>.
+            This tests the opposite relationship as
+            <literal>MBRWithin()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4442,7 +4444,11 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangles of the two geometries
             <replaceable>g1</replaceable> and
-            <replaceable>g2</replaceable> overlap.
+            <replaceable>g2</replaceable> overlap. The term
+            <emphasis>spatially overlaps</emphasis> is used if two
+            geometries intersect and their intersection results in a
+            geometry of the same dimension but not equal to either of
+            the given geometries.
           </para>
 
           <remark role="help-description-end"/>

@@ -4465,7 +4471,11 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangles of the two geometries
             <replaceable>g1</replaceable> and
-            <replaceable>g2</replaceable> touch.
+            <replaceable>g2</replaceable> touch. Two geometries
+            <emphasis>spatially touch</emphasis> if the interiors of the
+            geometries do not intersect, but the boundary of one of the
+            geometries intersects either the boundary or the interior of
+            the other.
           </para>
 
           <remark role="help-description-end"/>

@@ -4488,6 +4498,8 @@
             Returns 1 or 0 to indicate whether the Minimum Bounding
             Rectangle of <replaceable>g1</replaceable> is within the
             Minimum Bounding Rectangle of <replaceable>g2</replaceable>.
+            This tests the opposite relationship as
+            <literal>MBRWithin()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4521,26 +4533,29 @@
       </para>
 
       <para>
-        Currently, MySQL does not implement these functions according to
-        the specification. Those that are implemented return the same
-        result as the corresponding MBR-based functions. This includes
-        functions in the following list other than
-        <literal>Distance()</literal> and <literal>Related()</literal>.
+        The return values 1 and 0 indicate true and false, respectively.
       </para>
 
-      <remark role="note">
-        Crosses() is an exception here: It exists but MBRCrosses() does
-        not.
-      </remark>
+      <note>
+        <para>
+          Currently, MySQL does not implement these functions according
+          to the specification. Those that are implemented return the
+          same result as the corresponding MBR-based functions. This
+          includes functions in the following list other than
+          <literal>Distance()</literal> and
+          <literal>Related()</literal>.
+        </para>
 
-      <para>
-        These functions may be implemented in future releases with full
-        support for spatial analysis, not just MBR-based support.
-      </para>
+        <remark role="note">
+          Crosses() is an exception here: It exists but MBRCrosses()
+          does not.
+        </remark>
 
-      <para>
-        The return values 1 and 0 indicate true and false, respectively.
-      </para>
+        <para>
+          These functions may be implemented in future releases with
+          full support for spatial analysis, not just MBR-based support.
+        </para>
+      </note>
 
       <remark role="help-category" condition="Geometry relations@Geographic Features"/>
 

@@ -4562,7 +4577,8 @@
           <para>
             Returns 1 or 0 to indicate whether
             <replaceable>g1</replaceable> completely contains
-            <replaceable>g2</replaceable>.
+            <replaceable>g2</replaceable>. This tests the opposite
+            relationship as <literal>Within()</literal>.
           </para>
 
           <remark role="help-description-end"/>

@@ -4803,7 +4819,8 @@
           <para>
             Returns 1 or 0 to indicate whether
             <replaceable>g1</replaceable> is spatially within
-            <replaceable>g2</replaceable>.
+            <replaceable>g2</replaceable>. This tests the opposite
+            relationship as <literal>Contains()</literal>.
           </para>
 
           <remark role="help-description-end"/>


Thread
svn commit - mysqldoc@docsrva: r5804 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul10 Apr