Bug report #21100

field calculator doesn't load values for gpkg containing blank spaces or n dash (hypen) in field names

Added by Martina Savarese about 1 year ago. Updated 12 months ago.

Status:Closed
Priority:Normal
Assignee:Alessandro Pasotti
Category:Vectors
Affected QGIS version:3.5(master) Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:Yes Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:28918

Description

Hi,
field calculator, expression based filter and query builder don't load values for gpkg containing blank spaces or n dash (hyphen) in field names.

Furthermore the categorized renderer on these fields results in a simple marker renderer (see also #14737)

prova2.gpkg (96 KB) Martina Savarese, 2019-01-25 07:05 PM

field_d.PNG (69.2 KB) Martina Savarese, 2019-01-25 07:10 PM

field_f.PNG (62.5 KB) Martina Savarese, 2019-01-25 07:10 PM

Cat_2.PNG (25.8 KB) Martina Savarese, 2019-01-25 08:33 PM

Cat_3.PNG (24.8 KB) Martina Savarese, 2019-01-25 08:34 PM

Associated revisions

Revision b5142664
Added by Alessandro Pasotti 12 months ago

Quote field name identifiers in ORDER BY and MAX/MIN queries

Fixes #21100

History

#1 Updated by Giovanni Manghi about 1 year ago

  • Category changed from Unknown to Vectors
  • Status changed from Open to Feedback
  • Operating System deleted (windows 10 64bit)

Is the symbology problem also confirmed on 3.4.4?

#2 Updated by Martina Savarese about 1 year ago

Yes, for both fields: the one containing blank space and the one containing n dash (hypen) in field names. For those the resulting style is the same as single symbol

#3 Updated by Alexis Roy-L about 1 year ago

This also seems to happen with Spatialite (as they are all based on sqlite) and exporting such layers to a MSSQL database toggle the "Import was succesful" message but the layer does not appear in the browser panel after refresh.

Memory layer and shapefiles were ok.

But the databases are in the SQL database itself but are not displayed in the browser after a restart.

This might be related to how SQL are handled by QGIS.

Hope this helps.

#4 Updated by Jürgen Fischer 12 months ago

  • Description updated (diff)

#5 Updated by Alessandro Pasotti 12 months ago

  • Assignee set to Alessandro Pasotti

#6 Updated by Alessandro Pasotti 12 months ago

  • Affected QGIS version changed from 3.4.4 to 3.5(master)
  • Pull Request or Patch supplied changed from No to Yes

#7 Updated by Alessandro Pasotti 12 months ago

  • % Done changed from 0 to 100
  • Status changed from Feedback to Closed

Also available in: Atom PDF