Opened 15 years ago
Closed 14 years ago
#589 closed defect (worksforme)
SQLServerSpatial does not support same table in 2 schemas.
| Reported by: | chriserickson | Owned by: | brentrobinson |
|---|---|---|---|
| Priority: | major | Milestone: | 3.6.0 |
| Component: | FDO API | Version: | 3.4.0 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
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.
Change History (2)
comment:1 by , 14 years ago
| Milestone: | 3.5.0 → 3.6.0 |
|---|---|
| Owner: | changed from to |
comment:2 by , 14 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Setting class name to "Schema:Parcels" should work.