[fdo-trac] #756: SQLServerSpatial: Expose synonyms as FDO classes.

[FDO]

#756: SQLServerSpatial: Expose synonyms as FDO classes.
---------------------------------+------------------------------------------
   Reporter:  brentrobinson      |       Owner:  brentrobinson                                 
       Type:  enhancement        |      Status:  assigned                                      
   Priority:  minor              |   Milestone:  3.7.0                                         
  Component:  SQLServer Spatial  |     Version:  3.7.0                                         
   Severity:  3                  |    Keywords:  SQL Server 2008 SQLServerSpatial synonym class
External_id:                     |  
---------------------------------+------------------------------------------

Comment(by brentrobinson):

 Revision: 6021
 Author: brentrobinson
 Date: 12:41:19 PM, Wednesday, March 30, 2011
 Message:
 Ticket#756: SQLSeverSpatial: Tuned the reading of physical spatial
 contexts by implementing partial bulk loading. When asked to retrieve a
 particular spatial context, it and a number of other spatial contexts are
 now retrieved.

 More performance enhancements for synonyms are also included for the case
 where:

    - a GetClassNames command is executed for all schemas
    - a partial DescribeSchema command is executed where classes for some
 of the synonyms in the datastore are requested.

 The GetClassNames causes all synonyms in the datastore to be read and
 cached. The partial DescribeSchema causes the base object for each
 requested synonym to be looked up. These base object fetches are bulked up
 so that the base objects for the requested synonym plus 24 other candidate
 synonyms are fetched at once. However, the candidates were
 chosen from all synonyms in the datastore, most of which are not being
 described.

 The fix was to add a flag to each synonym indicating whether it is cached
 for listing only or for retrieving its components (e.g. columns). Only
 synonyms cached for component retrieval are picked up as candidates when
 fetching base objects, meaning fewer fetches to get the base objects for
 the synonyms to describe.
 ----
 Modified :
 /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/SchemaMgr/Ph/Owner.cpp
 Modified :
 /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/SchemaMgr/Ph/Owner.h
 Modified :
 /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/SchemaMgr/Ph/Rd/SpatialContextReader.cpp
 Modified :
 /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/SchemaMgr/Ph/Rd/SpatialContextReader.h
 Modified : /trunk/Utilities/SchemaMgr/Inc/Sm/Ph/DbObject.h
 Modified : /trunk/Utilities/SchemaMgr/Inc/Sm/Ph/Owner.h
 Modified : /trunk/Utilities/SchemaMgr/Src/Sm/Ph/DbObject.cpp
 Modified : /trunk/Utilities/SchemaMgr/Src/Sm/Ph/Owner.cpp
 Modified : /trunk/Utilities/SchemaMgr/Src/Sm/Ph/Synonym.cpp
 Modified : /trunk/Utilities/SchemaMgr/Src/Sm/Ph/SynonymBaseLoader.cpp

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/756#comment:3>
FDO <http://fdo.osgeo.org/>
Feature Data Objects