Opened 14 years ago
Last modified 14 years ago
#681 assigned defect
SQLServer Spatial Provider and Associations
Reported by: | crispinatime | Owned by: | brentrobinson |
---|---|---|---|
Priority: | major | Milestone: | 3.5.0 |
Component: | SQLServer Spatial | Version: | 3.5.0 |
Severity: | 3 | Keywords: | |
Cc: | External ID: |
Description
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")); }
Change History (2)
comment:1 by , 14 years ago
Owner: | changed from | to
---|
comment:2 by , 14 years ago
Status: | new → assigned |
---|
Note:
See TracTickets
for help on using tickets.