-
-
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
QGIS3.4 Organize columns, data integrity compromised #28493
Comments
Author Name: Giovanni Manghi (@gioman) Does it happens on 2.18?
|
Author Name: Soares SOares (Soares SOares) Yes, Giovanni. And also in 3.4LTR |
Author Name: Giovanni Manghi (@gioman) Soares SOares wrote:
my question was about 2.18, not 3.4 |
Author Name: Soares SOares (Soares SOares) Yes, it happens in 2.18. |
Author Name: Giovanni Manghi (@gioman) Soares SOares wrote:
I assume that the raw data integrity is not compromised(?)
|
Author Name: Alessandro Pasotti (@elpaso) I cannot reproduce on current master, can you please add a sample project and sample data and a video that demonstrate the issue? |
Author Name: Soares SOares (Soares SOares) Ok, I will send to you on monday. |
Author Name: Soares SOares (Soares SOares) Hello Alessandro. At the moment I can't make a video, but there is a project with a shapefile.
The content atribute in selected cell (col_18) will be sended to 'col_11'
|
Author Name: Soares SOares (Soares SOares) 2.14 just fine |
Author Name: Alessandro Pasotti (@elpaso) Confirmed on master thanks for the demo data.
|
Author Name: Alessandro Pasotti (@elpaso)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Luigi Pirelli (@luipir) is it confirmed data loss or compromising? if so, the issue shouldn't have normal priority |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Julien Cabieces (Julien Cabieces) Proposed PR : #8725 |
Author Name: Julien Cabieces (Julien Cabieces) Applied in changeset fba4b25.
|
Author Name: Soares SOares (Soares SOares) I've Tested 2.18.27 and the bug still there. The bug also persists in 3.4.3 I've used the same file in bug report.
|
Author Name: Julien Cabieces (Julien Cabieces) The correction had not been backported in 2.18.27 but is present in 3.4.4 (not 3.4.3)
|
Author Name: Soares SOares (Soares SOares)
Original Redmine Issue: 20673
Affected QGIS version: 3.5(master)
Redmine category:attribute_table
Assignee: Julien Cabieces
When you use 'Organize columns' and 'move selection to top' in atribute table you can crash your data integrity.
To reproduce this bug you will need a layer with more than 14 columns and more than
45 rows. That is the specification of our smaler table. We have tried with
a smaller table and we don't get any error.
1 - pick up the atribute table (postgres with geometry or shapefile),
right click in a column name and select 'Organize columns...'
2 - Reorder the columns. Thinking in column position like a list, try a
sequence that bring to initial positions the end elements. In a example
14,12,5,1,2...
3 - Back to the table, start edition.
4 - Click at QGIS numerator of feature in table. this will turn editable the cell of
the column 14 (remind the example above),
5 - Chose in menu table 'move selection to top'
6 - look for the atribute's of column 14, it will apear in another column
of the same selected object.
Related issue(s): #28553 (relates)
Redmine related issue(s): 20733
The text was updated successfully, but these errors were encountered: