Changes between Version 4 and Version 5 of Release/2.2Beta/Notes


Ignore:
Timestamp:
May 3, 2010, 1:04:00 PM (14 years ago)
Author:
trevorwekel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Release/2.2Beta/Notes

    v4 v5  
    3434[wiki:MapGuideRfc74 RFC 74] introduces a boolean "cascade" parameter to !MgResourceService.!MoveResource().  If cascade is enabled, dependant resources will be updated to point at the new location for the moved resource. Since this is new API, there is no impact on existing code.
    3535
    36 [wiki:MapGuideRfc78 RFC 77] allows !MgFeatureService.!CreateFeatureSource() to create a feature source without defining the feature class and spatial context.  The previous implementation would throw an !MgInvalidArgumentException.  '''This behaviour change may affect existing code.'''[[BR]] [[BR]]
     36[wiki:MapGuideRfc78 RFC 77] allows !MgFeatureService.!CreateFeatureSource() to create a feature source without defining the feature class and spatial context.  The previous implementation would throw an !MgInvalidArgumentException.  '''This behaviour change may affect existing code.'''[[BR]]
    3737
    3838[wiki:MapGuideRfc78 RFC 78] introduces explicit transaction management for Feature Service.  A new !MgTransaction object is created and !MgFeatureService !ExecuteSqlQuery, !ExecuteSqlNonQuery, and !UpdateFeatures are overloaded to use the new transaction object.  Since this is new API, there is no impact on existing code.
    3939
    40 [wiki:MapGuideRfc79 RFC 79] adds more detailed exception classes derived from MgFdoException.  The derived classes provide more information than the generic MgFdoException.  Existing code should continue to work with MgFdoException and should be updated to make use of the derived exception classes.
     40[wiki:MapGuideRfc79 RFC 79] adds more detailed exception classes derived from !MgFdoException.  The derived classes provide more information than the generic !MgFdoException.  Existing code should continue to work with !MgFdoException and should be updated to make use of the derived exception classes.
    4141
    4242[wiki:MapGuideRfc80 RFC 80] adds parameter binding support to !MgFeatureService !ExecuteSqlQuery and !ExecuteSqlNonQuery.  Since this is new API, there is no impact on existing code.
    … …  
    4444[wiki:MapGuideRfc82 RFC 82] extends the !MapGuide readers to support property access by index in addition to property name.  Accessing properties by index instead of property name may be faster for tight loop processing.  Since this is new API, there is no impact on existing code.
    4545
    46 [wiki:MapGuideRfc84 RFC 84] adds database row fetch size to !MgFeatureQueryOptions and !MgFeatureService.ExecuteSqlQuery.  Specifying a fetch size may improve FDO performance by reducing database round trips.    Since this is new API, there is no impact on existing code.
     46[wiki:MapGuideRfc84 RFC 84] adds database row fetch size to !MgFeatureQueryOptions and !MgFeatureService.!ExecuteSqlQuery.  Specifying a fetch size may improve FDO performance by reducing database round trips.    Since this is new API, there is no impact on existing code.
    4747
    4848[wiki:MapGuideRfc87 RFC 87] adds to the schema returned from the HTTP GETSITEINFO request.  If version 2.2.0 of GETSITEINFO is used, the following addiitional information will be returned working set, virtual memory, server cache size and server cache dropped entries.  Since this is new version of GETSITEINFO, there is no impact on existing code.
    … …  
    7676}}}
    7777
    78 These API changes will impact:
     78The RFC 87 API changes will impact:
    7979 * Viewers
    8080 * Sample applications