[fdo-trac] #681: SQLServer Spatial Provider and Associations

[FDO]

#681: SQLServer Spatial Provider and Associations
---------------------------------+------------------------------------------
   Reporter:  crispinatime       |       Owner:  danstoica
       Type:  defect             |      Status:  new      
   Priority:  major              |   Milestone:  3.5.0    
  Component:  SQLServer Spatial  |     Version:  3.5.0    
   Severity:  3                  |    Keywords:           
External_id:                     |  
---------------------------------+------------------------------------------
 Hi,
 The SQLServer provider reports in it's capabilities that it supports
 Associations (and it does allow them to be created in the FDO schema).

 However, when Executing a reader you get an unhelpful "Case not handled
 yet" thrown when the association property is in the class.

 There are three occurrences of "Case not handled yet" in the
 RDBMS/SQLServer provider but this is the guilty one in this case:

 Surely a provider should not report capabilities if they are not
 queryable?

  Crispin


 {{{
 void FdoRdbmsFilterProcessor::AppendAssociationProperty( const
 FdoSmLpClassDefinition* currentClass, const
 FdoSmLpAssociationPropertyDefinition* assocProp, bool useOuterJoin, bool
 inSelectList )
 {
     throw FdoFilterException::Create(NlsMsgGet(FDORDBMS_20, "Case not
 handled yet"));
 }

 }}}

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/681>
FDO <http://fdo.osgeo.org/>
Feature Data Objects