[QGIS-trac] [Quantum GIS] #3782: char/varchar must not be saved with ASCII 0 in Spatialite after editing

[Quantum GIS]

#3782: char/varchar must not be saved with ASCII 0 in Spatialite after editing
------------------------------------------------+---------------------------
   Reporter:  Sfkeller                          |              Owner:  nobody       
       Type:  bug                               |             Status:  new          
   Priority:  major: does not work as expected  |          Milestone:  Version 1.7.0
  Component:  Data Provider                     |            Version:  Trunk        
   Keywords:  char, varchar, spatialite         |   Platform_version:               
   Platform:  All                               |           Must_fix:  Yes          
Status_info:  0                                 |  
------------------------------------------------+---------------------------
 All char/varchar values of a spatialite datasource seem to get ASCII 0
 ('NUL') appended after editing with QGIS default attribute editor. This
 type of 'null-terminated string' does not belong here.

 This turns SQL queries (like SELECT...FROM...WHERE f = 'searchstring')
 unusable since 'searchstring' get's compared with 'searchstring\0'.

 How to reproduce this unwanted behaviour: Create a Spatialite dataset with
 a table consisting of fields of type varchar and/or char. Then populate
 the dataset, open it in QGIS and edit a feature. After saving this
 feature, all values of type char/varchar get a NUL code appended. This can
 be visualized when exporting to CSV using Spatialite GUI tool and viewing
 it with a text editor.

-- 
Ticket URL: <https://trac.osgeo.org/qgis/ticket/3782>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS supporting GDAL/OGR, PostGIS, and GRASS formats, and Web Services