#487 closed defect (fixed)
SQLServerSpatial: Fix crash when selecting features with null geometries
| Reported by: | brentrobinson | Owned by: | brentrobinson |
|---|---|---|---|
| Priority: | major | Milestone: | 3.5.0 |
| Component: | SQLServer Spatial | Version: | 3.4.0 |
| Severity: | 2 | Keywords: | select null geometry |
| Cc: | External ID: |
Description
A stale pointer problem can handle when an FdoISelect is performed on a feature class where a feature after the 100th feature has a null geometry.
Change History (4)
comment:1 by , 15 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 15 years ago
Fix also submitted to 3.4 stream. See https://trac.osgeo.org/fdo/changeset/4586.
Note:
See TracTickets
for help on using tickets.
Revision: 4506 Author: brentrobinson Date: 2:29:00 PM, Thursday, March 26, 2009 Message: Ticket#487:Initialize copy of caller's defined geometries before converting next batch of fetched geometries from RDBMS to FDO.
Modified : /trunk/Providers/GenericRdbms/Src/ODBCDriver/geom.c Modified : /trunk/Providers/GenericRdbms/Src/SQLServerSpatial/ODBCDriver/geom.c