#763 closed enhancement (fixed)
Change SQL Spatial Server to use Microsoft geometry format
Reported by: | romicadascalescu | Owned by: | romicadascalescu |
---|---|---|---|
Priority: | major | Milestone: | 3.7.0 |
Component: | SQLServer Spatial | Version: | 3.7.0 |
Severity: | 3 | Keywords: | |
Cc: | External ID: |
Description
- Add a convertor from/to FDO/Microsoft geometry format
- Pass the geometry at insert, update and spatial select using binds to avoid
ToString() conversion
- Move to a new SQL driver DRIVER={SQL Server Native Client 10.0}
- This driver behaves a bit different than the standard one (at least we can
bind big geometries) and a few things had to be fixed.
Note: in order to be able to use the provider you need to install Microsoft SQL Server Native Client 10.0
Change History (2)
comment:1 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
- We moved to the new SQL driver DRIVER={SQL Server Native Client 10.0} to be able to bind geometries bigger than 8000. This is not possible with default ODBC driver since image (the single format which can bind more than 8000 bytes) cannot be converted to Microsoft geometry.
- Moving to Microsoft geometry format we are now able to support Z &/ M coordinates.
Note:
See TracTickets
for help on using tickets.