Changes between Version 3 and Version 5 of Ticket #1528
- Timestamp:
- Mar 26, 2007, 8:55:23 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1528
- Property Status assigned → closed
- Property Cc added
- Property Version unspecified → 1.4.0
- Property Milestone 1.5.0 → 1.4.1
- Property Resolution → fixed
- Property Severity critical → major
-
Ticket #1528 – Description
v3 v5 1 {{{ 2 The -where clause behaves instable in some cases. 3 When used against MySQL or PostgreSQL, with OGR dialect of SQL, segmantation fault is thrown. 4 It should be handled cleanly, if unsupported dialect is used. 1 The -where clause behaves instable in some cases. When used against MySQL or PostgreSQL, with OGR dialect of SQL, segmantation fault is thrown. It should be handled cleanly, if unsupported dialect is used. 5 2 6 3 Example of crash: 7 8 -------------------------------------------------------------------- 4 {{{ 9 5 madmappers:/home/work# /opt/gdal-r11007_x86-linux/bin/ogr2ogr -f MySQL MYSQL:sptest,user=sptest,password=,host=127.0.0.1 -nln locust -update -overwrite FAO_DBsummary.shp -where 'OGR_GEOMETRY=POINT' 10 6 Segmentation fault … … 13 9 [Switching to Thread 1090607360 (LWP 28956)] 14 10 0x40357753 in OGRFeature::GetFieldAsString () from /opt/gdal-r11007_x86-linux/lib/libgdal.so.1 15 -------------------------------------------------------------------- 16 11 }}} 17 12 The major goal of this report is to review and fix potential problems with handling SQL queries in OGR by various ORG drivers. 18 }}}