-
-
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 moving fields #21768
Comments
Author Name: Giovanni Manghi (@gioman) Can you please specify the exact steps to replicate and/or attach a sample dataset? thanks.
|
Author Name: Jakub Kosik (@jakosek) As I said, there is no rule. I cannot specify exact steps, but this only happens when I digitise a lot: most vertex edit, some reshape, split, add ring. Problem show up only when I hit save button. I am restricted to share all my database, but I attached main tables export ("GeometriaDzialki" and "Zdjecia", as I noticed on polygon and line layers). |
Author Name: Jakub Kosik (@jakosek) After some research: only new added features are broken, eg. from copy-paste or split. They are displayed properly until save. |
Author Name: Giovanni Manghi (@gioman) Jakub Kosik wrote:
I tried to split over and over the line layer "Zdjecia" and after saves attributes tables always looks fine to me. Maybe a screencast would help understanding how to replicate the issue. |
Author Name: Jakub Kosik (@jakosek) It's almost impossible to replicate this issue, so there is no hope to screencast. Issue happens once in a hundred saves, but in 50 person team it happens way too often :/ PS. Main table is "GeometriaDzialki". Strange is, as I wrote in beginning - without PrimaryKey problem does not exists. |
Author Name: Jakub Kosik (@jakosek) Not same at all - I got mess in fields of single object, not mixed with other objects. Also geometry looks unbroken (but in my project objects disappeared due to attribute defined styles). |
Author Name: Jakub Kosik (@jakosek) Here is some screencast - only moment of save edits. After split attributes are on places. On save - move feft (one feature saved correctly, one broken). |
Author Name: Giovanni Manghi (@gioman) Jakub Kosik wrote:
Yes, it seems the same issue. From the other ticket "When attributes are getting mixed with other objects, it is often the record above or below in the (table)" that is what happens exactly in the screencast you posted here. I tried again and again with the table "GeometriaDzialki" and I wasn't able to replicate. Please test again on QGIS master and report back. |
Author Name: Giovanni Manghi (@gioman) closing for lack of feedback, please reopen if necessary.
|
Author Name: Jakub Kosik (@jakosek) Problem still exists in 2.14.3 I changed simple data layer into editable spatialite view - same effect of moving fields.
|
Author Name: Gregor Sanders (Gregor Sanders) This problem can be replicated consistently with the following steps:
Note, and perhaps this is a key to solving the bug: This behaviour is only reproduced when editing a non-geometry table in a spatialite database, not in a regular sqlite database.
|
Author Name: Giovanni Manghi (@gioman) Using recent QGIS releases this (and similar) issues seems to have "gone", at least I cannot replicate them anymore.
|
…eType & GetFeature Fixes Redmine qgis#21768 and qgis#9849 Due to confusion in the WFS 2.0 sepecification the situation is that WFS 2.0 servers 'randomly' recognize TYPENAME or TYPENAMES depending on DescribeFeatureType and GetFeature requests. So emit both parameters as tests show that it fixes issues and doesn't seem to cause harm.
…eType & GetFeature Fixes Redmine #21768 and #9849 Due to confusion in the WFS 2.0 sepecification the situation is that WFS 2.0 servers 'randomly' recognize TYPENAME or TYPENAMES depending on DescribeFeatureType and GetFeature requests. So emit both parameters as tests show that it fixes issues and doesn't seem to cause harm.
…eType & GetFeature Fixes Redmine #21768 and #9849 Due to confusion in the WFS 2.0 sepecification the situation is that WFS 2.0 servers 'randomly' recognize TYPENAME or TYPENAMES depending on DescribeFeatureType and GetFeature requests. So emit both parameters as tests show that it fixes issues and doesn't seem to cause harm.
Author Name: Jakub Kosik (@jakosek)
Original Redmine Issue: 13741
Affected QGIS version: 2.12.0
Redmine category:data_provider/spatialite
When using spatialite database I've found strange behaviour: sometime, with no rule, fields are saved incorrectly. This is old problem, same on 2.8, maybe earlier.
This only happens when I use table with (autoincremented) primary key. In 2.8 there was workaround - use table without primary key, but it is impossible in 2.12 (related to #21527).
In example you can find fields "move left" on first two elements. Left or right move, with no rule.
The text was updated successfully, but these errors were encountered: