Opened 16 months ago

#930 new defect

[SQL Server]: Listing spatial contexts fails if the database contains one or more tables with dots in its name

Reported by: jng Owned by: danstoica
Priority: major Milestone: 4.1.0
Component: SQLServer Spatial Version: 4.0.0
Severity: 3 Keywords:
Cc: External ID:

Description

If I have a SQL Server db with a spatial table named "Foo.Bar", the FDO provider won't be able to enumerate spatial contexts for the whole database.

Turning on SQL Server profiler shows that the FDO provider executes a SQL query to get the srid of "dbo"."Foo"."Bar", when it should actually be "dbo"."Foo.Bar"

Change History (0)

Note: See TracTickets for help on using tickets.