Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Field Calculator doesn't work - spatiaLite #17191

Closed
qgib opened this issue Aug 7, 2013 · 4 comments
Closed

Field Calculator doesn't work - spatiaLite #17191

qgib opened this issue Aug 7, 2013 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers

Comments

@qgib
Copy link
Contributor

qgib commented Aug 7, 2013

Author Name: Jonathan Moules (Jonathan Moules)
Original Redmine Issue: 8422
Affected QGIS version: master
Redmine category:data_provider/spatialite


I have a SpatiaLite database. When I try and use field calculator on it absolutely nothing happens. I don't get either an error nor any changes to the database.
I've tried using the area calculator, or simply entering the value of "1" (sans quotes). No change.

If I have set it to "create new column" it will create the column, but the values will all be NULL. Update column does nothing at all.

Field Calculator works fine on shapefiles.

Weekly build a13cdf8 - windows 7, x64.


@qgib
Copy link
Contributor Author

qgib commented Aug 8, 2013

Author Name: Giovanni Manghi (@gioman)


I cannot confirm using for example the SL dataset you added to other tickets today. Tested on qgis master on both Linux and Windows.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Aug 15, 2013

Author Name: Jonathan Moules (Jonathan Moules)


Now updated to d61cb25. A little more testing shows the nature of the problem.

The SL driver is taking a very long time to update the SL database (using https://issues.qgis.org/attachments/6139/Compass_logs_-_Copy.7z from my other ticket).

There are only ~51,000 features in the database.

Process:

  1. Add dataset
  2. Toggle editing
  3. Create field "test" -> Integer
  4. Field Calculator -> value of "5555" into the "test" field.
  5. Turn off editing -> Save changes.

At this point several bad things happen:

  • QGIS locks up for five minutes (literally 5 minus) writing to the SL.
  • If I attempt to close the attribute window during this time, QGIS crashes.
  • If you look at the attached you can see the resource use during the save. This actually covers two saves (the bits where the IO bar is purple are where it is saving). Notice how RAM use keeps going up but isn't freed afterwards. Leak? No other tasks were performed during this QGIS session.

Nothing else is accessing the SL Dataset. The machine is a high end workstation; the dataset is on an SSD. Shouldn't it just take a few seconds to do this update? "update processed set tests = 9876;" in spatialite_gui takes 6.6 seconds.


  • 6160 was configured as Clipboard16.png

@qgib
Copy link
Contributor Author

qgib commented Aug 15, 2013

Author Name: Giovanni Manghi (@gioman)


Just updated on both Linux and Windows and I cannot confirm this issue. It takes around the same amount of time as SL gui to save on QGIS.

@qgib
Copy link
Contributor Author

qgib commented Oct 8, 2014

Author Name: Giovanni Manghi (@gioman)


closing for lack of feedback, please reopen if necessary.


  • resolution was changed from to worksforme
  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers labels May 24, 2019
@qgib qgib closed this as completed May 24, 2019
JamesShaeffer pushed a commit to JamesShaeffer/QGIS that referenced this issue Nov 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant