Changes between Version 1 and Version 2 of MapGuideRfc123

Timestamp:

10/24/11 05:47:47 (13 years ago)

Author:

jng

Comment:

--

MapGuideRfc123

@@ -69 +69 @@
 === Setting up the FDO join query ===
 
-We use the FdoIExtendedSelect interface to perform the FDO join query. The extended feature class already uses an optional prefix on the secondary class as a means of disambiguating identically named properties on both sides of the join. 
+We use the FdoIExtendedSelect interface to perform the FDO join query. The extended feature class already uses an optional prefix on the secondary class as a means of disambiguating identically named properties on both sides of the join. We will use this same prefix to alias the secondary property names to prevent ambiguous names during query preparation.
 
 Properties from the primary class will be specified as the following FDO computed property:
@@ -105 +105 @@
 Iteration logic for the normal case (not 1:1), is simply to pass over to the underlying reader's ReadNext() method. Tracking of identity property values is not required for this case.
 
-Though not reflective of what the final implementation may be performance-wise, support for FDO joins has already been implemented in mg-desktop and the benefits there are clear. The performance times for a 17000 feature by 16000 feature join (of [http://code.google.com/p/mg-desktop/source/browse/DesktopTestData/ParcelsJoinTest.sqlite this dataset]) are outlined below.
+Though not reflective of what the final implementation may be performance-wise, support for FDO joins has already been implemented in [http://mg-desktop.googlecode.com mg-desktop] and the benefits there are clear. The performance times for a 17000 feature by 16000 feature join (of [http://code.google.com/p/mg-desktop/source/browse/DesktopTestData/ParcelsJoinTest.sqlite this dataset]) are outlined below.
 
 || Test Case              || SDF    || SQLite ||