Changes between Version 8 and Version 9 of FDORfc39

Timestamp:

Jun 24, 2009, 2:31:20 PM (15 years ago)

Author:

danstoica

Comment:

--

FDORfc39

@@ -115 +115 @@
 == Implications ==
 
-RDBMS providers supporting natively the RELATE spatial operator can implement the new API by examining the mask:
+The actual implementation of the RELATE operator in the providers is easy. First, retrieve  
 
 {{{
       FdoSpatialCondition*  pFilter = ...
-      Int32  mask = pFilter->GetRelateMask();
+      FdoSpatialOperations op = pFilter->GetOperation();
+      if ( op == FdoSpatialOperations_Relate )
+      {
+          Int32  mask = pFilter->GetRelateMask();
+          ...
+      }
 }}}
- 
-SqlServer Spatial or PostGIS providers need the string pattern matrix to pass it as input for STRelate() and ST_Relate() respectively:
+
+Depending on the provider the coding will be different:
+
+1. RDBMS providers supporting natively the RELATE spatial operator can implement the new API by examining the mask:
+
+   a) SqlServer Spatial or PostGIS providers need the string pattern matrix to pass it as input for STRelate() and ST_Relate() respectively:
  
 {{{
@@ -130 +139 @@
 }}}
 
-Oracle providers will inspect the bitmapped mask and extract the spatial operators to build the SQL like:
+   b) An Oracle provider will inspect the bitmapped mask and extract the spatial operators to build the SQL like:
 
 {{{
@@ -136 +145 @@
 }}}
 
+2) The providers not supporting natively RELATE will need to expand the RELATE filter into a OR filter with multiple basic spatial operations.
 
 == Test Plan ==
-[TODO]
 
 == Funding/Resources ==