Bug report #17144
Deleting fields from empty layer causes first attribute to be renamed.
| Status: | Closed | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: | - | ||
| Category: | Vectors | ||
| Affected QGIS version: | 3.1(master) | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | no timely feedback |
| Crashes QGIS or corrupts data: | Yes | Copied to github as #: | 25043 |
Description
Hi all,
I have the following problem: if I delete one or more fields from a layer (shp) that contains no one record, the name of the first fields is changed when I save the data.
It does not happen if the layer contains at least one object or if before/after delating field I add at least another field.
How can I fix the problem?
Thanks,
Elisa
History
#1
Updated by Giovanni Manghi about 7 years ago
- Subject changed from QGIS 2.18.12 - deleting fields from empty layer to Deleting fields from empty layer causes first attribute to be renamed.
- Crashes QGIS or corrupts data changed from No to Yes
- Pull Request or Patch supplied changed from Yes to No
- Operating System deleted (
WIN10) - Assignee deleted (
Victor Olaya) - Category changed from Processing/QGIS to Vectors
Seen also on Linux and on 2.14 and master. In all my tests the first attribute was "id" and was changed to "sometrangechard+d".
#2
Updated by Luca Lanteri over 6 years ago
- File 2018-02-26_183226.jpg added
Confirmed on 3.1.
the original field name "id" now has a special character (See attached file)
#3
Updated by Giovanni Manghi over 6 years ago
- Affected QGIS version changed from 2.18.12 to 3.1(master)
#4
Updated by Giovanni Manghi about 6 years ago
- Status changed from Open to Feedback
Please try on QGIS 3.4.1, if the issue is still valid change the affected version, thanks.
#5
Updated by Jürgen Fischer over 5 years ago
- Status changed from Feedback to Closed
- Resolution set to no timely feedback
Bulk closing 82 tickets in feedback state for more than 90 days affecting an old version. Feel free to reopen if it still applies to a current version and you have more information that clarify the issue.