[fdo-trac] #589: SQLServerSpatial does not support same table in 2 schemas.

[FDO]

#589: SQLServerSpatial does not support same table in 2 schemas.
-----------------------------+----------------------------------------------
   Reporter:  chriserickson  |       Owner:  gregboone
       Type:  defect         |      Status:  new      
   Priority:  major          |   Milestone:  3.5.0    
  Component:  FDO API        |     Version:  3.4.0    
   Severity:  3              |    Keywords:           
External_id:                 |  
-----------------------------+----------------------------------------------
 I have a database with a layer (Parcels) which exists in 2 schemas.

 On a select command, when you call SetFeatureClassName and hand in the
 class's qualified name, it hands in an (unqualified) name of 'Parcels'.
 An error is then thrown "class parcels found in multiple schemas".

 There is no workaround that I've found, I've tried setting my default
 schema in SQL and handing an a fully qualified name ("Schema.Parcels"),
 which then just throws an error that it could not find the layer.

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