Bug report #8923
Updated by Giovanni Manghi almost 7 years ago
*How to reproduce:*
* Add a spatialite layer (e.g. OSM import or create a new one)
* Turn on editing
* Open the field calculator
* Add a new column. ( I took: Data type: double, expression: "randf(5,10)" )
* Turn off editing (Save changes)
* Result: New column shown in the attribute table
* Remove the layer from the project
* Re-load the layer into the project
* Result: New column disappeared
Checking in the sqlite data itself, the column is actually added and the expression data is present.
*Expected behavior:*
The newly added column should be visible
*Note:*
The problems seems to be the table @geometry_columns_field_infos@ which does not contain the new column, but the spatialite provider loads the information from there. I think, that it should be updated by a trigger, but my spatialite knowledge ends pretty much there.
*Caveat:*
Make sure you have a more recent build than commit:249526b (Oct, 20) to be able to add columns
Can somebody verify this behavior. I want to be sure it is not a local issue before reporting it upstream.
* Add a spatialite layer (e.g. OSM import or create a new one)
* Turn on editing
* Open the field calculator
* Add a new column. ( I took: Data type: double, expression: "randf(5,10)" )
* Turn off editing (Save changes)
* Result: New column shown in the attribute table
* Remove the layer from the project
* Re-load the layer into the project
* Result: New column disappeared
Checking in the sqlite data itself, the column is actually added and the expression data is present.
*Expected behavior:*
The newly added column should be visible
*Note:*
The problems seems to be the table @geometry_columns_field_infos@ which does not contain the new column, but the spatialite provider loads the information from there. I think, that it should be updated by a trigger, but my spatialite knowledge ends pretty much there.
*Caveat:*
Make sure you have a more recent build than commit:249526b (Oct, 20) to be able to add columns
Can somebody verify this behavior. I want to be sure it is not a local issue before reporting it upstream.