-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Spatialite Integer columns cannot be used #17684
Comments
Author Name: Brian Freed (@bfreed) One exception: integer primary key still writes |
Author Name: Jürgen Fischer (@jef-n) Hm, I don't really understand. You're digitizing on a layer with NULL contraints, you aren't entering non-NULL values and cannot save? Isn't that what ought to happen? |
Author Name: Brian Freed (@bfreed) No, sorry, I wasn't clear. I have a layer I use for making Atlas Coverages. It's got not nulls and various triggers to force snapping to the correct page size. I've been working backwards for why it's always worked great in 1.8 but doesn't in 2. But in the end: I probably shouldn't have clouded the issue by mentioning the not null. Entering all my data, then having Spatialite bomb with a "page_num cannot be null" error, even though I gave it a page_num was just one of the steps along the way. :-) |
Author Name: Brian Freed (@bfreed) I just uninstalled the 64-bit version and downloaded the 32-bit installer. It doesn't seem to have the same problem. I should have specified 64-bit in platform, I guess. It appears to be a 64-bit only bug. |
Author Name: Matthias Kuhn (@m-kuhn) Some fixes have been applied to the spatialite provider (also affecting "whole number" type) between 2.0 and master. |
Author Name: Brian Freed (@bfreed) Although, it seems like Spatialite version 3 databases don't have editable views either now. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Brian Freed (@bfreed)
Original Redmine Issue: 9029
Affected QGIS version: 2.0.1
Redmine category:data_provider/spatialite
In 2.0, NULL values are written to any Spatialite columns defined as integers when an object is first created.
Subsequent editing of the same object saves integer columns correctly.
Text and real columns do not do this (in 2.0.1-Dufour)
If any integer column has a not null constraint, it's impossible to create new entities on that layer.
Tested Polygons & Linestrings, both projected coords and 4326. Tested creating layer in Spatialite-GUI v3, Spatialite-GUI v4, and directly in QGIS via New Spatialite layer. Same behavior.
Tested Master (Build 45582e5): Unfortunately, it's worse - all column types write NULL on creation.
The text was updated successfully, but these errors were encountered: