Opened 13 years ago
Closed 13 years ago
#3951 closed defect (fixed)
MS SQL Server 2008 Driver and f_table_schema
Reported by: | geographika | Owned by: | tamas |
---|---|---|---|
Priority: | normal | Milestone: | 1.8.1 |
Component: | default | Version: | 1.8.0 |
Severity: | normal | Keywords: | mssql driver geometry_columns f_table_schema |
Cc: | tamas |
Description
In the geometry_columns metadata table the f_table_schema is ignored.
In the example below the first record in the geometry_columns works with the connection string below and second does not.
[f_table_catalog], [f_table_schema] ,[f_table_name], [f_geometry_column],[coord_dimension],[srid],[geometry_type] DbName, any value can be put here, schemaname.mytable, GEOMFIELD , 2, 32768, MULTIPOLYGON DbName, schemaname, mytable, GEOMFIELD, 2, 32768, MULTIPOLYGON
conn_string = "MSSQL:server=W08-SQL08;database=DbName;Integrated Security=true;"
Sample Python connection (same issue with ogrinfo and command line):
ds = ogr.Open(conn_string) lyr = ds.GetLayerByName('schemaname.mytable') #schema name always has to be passed here
Change History (3)
comment:1 by , 13 years ago
Cc: | added |
---|
comment:2 by , 13 years ago
Owner: | changed from | to
---|
comment:3 by , 13 years ago
Milestone: | → 1.8.1 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Fixed in trunk (r21939) and branch 1.8 (r21938)