Feature request #6450

Allow QGIS to 'guess' field types for calculated fields in spatialite views

Added by Marie Silvestre over 4 years ago. Updated 6 months ago.

Status:Open Start Date:10/04/2012
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:SpatiaLite Data Provider
Target version:Future Release - Nice to have
Platform: Resolution:
Platform version: Pull Request or Patch supplied:No
Status info: Tag:

Description

When creating a view (spatial or not) within a sqlite database, calculated fields have no definite type because of the affinity typing rules of SQLite.
Those fields cannot be used by QGIS for symbology purposes thereafter.

Unless there is a way to by-pass this issue, I think it's realy a shame to populate the database with tables instead of views.

History

Updated by Pirmin Kalberer over 4 years ago

  • Target version changed from Version 1.8.0 to Version 2.0.0

Updated by Pirmin Kalberer over 4 years ago

  • Target version changed from Version 2.0.0 to Future Release - Nice to have

Updated by Jürgen Fischer over 3 years ago

  • Subject changed from Allow QGIS to 'guess' field types for calcutlated fields in spatialite views to Allow QGIS to 'guess' field types for calculated fields in spatialite views

Updated by Jürgen Fischer over 3 years ago

  • Priority changed from High to Normal

Updated by Jürgen Fischer over 3 years ago

  • Category set to SpatiaLite Data Provider

Updated by Médéric RIBREUX over 1 year ago

  • Status changed from Open to Feedback

Hello, bug triage...

in QGIS 2.13 master (and probably in 2.12.1), when I make a SQLite view, QGIS find attribute type without any problem...
Can you confirm ?

Updated by Médéric RIBREUX over 1 year ago

Oops, sorry for the noise: I've made tests with calculated fields and QGIS don't recognise them (even with a CAST function)...
Furthermore, in DBManager, the calculated field type is also empty.

So this feature request is still valid !

Updated by Médéric RIBREUX about 1 year ago

  • Status changed from Feedback to Open

Updated by Pieter Brusselman 6 months ago

Can someone estimate how much time it would take to solve this problem? Maybe we can look for a solution....

Also available in: Atom