Bug report #16822
Copy/paste features from a table in one project to another table in different project results in NULLs in all attributes
|Affected QGIS version:||2.18.10||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 #:||24721|
Seen this one before but it's been a long time.
The tables have identical structure but are in two different projects.
Every field is changed to NULL when the rows are posted to the new table.
Qgis build 7d67b02
#3 Updated by Patrick Dunford over 2 years ago
The issue occurs when pasting data from one project into another project when both are open at the same time in separate Qgis windows. This is demonstrated by the two attached projects which each have a single table attached to them, the two tables are copies of each other.
#4 Updated by Giovanni Manghi over 2 years ago
Patrick Dunford wrote:
I'll do that shortly but just a quick note that your system doesn't appear to be emailing me like it used to. I haven't had any notification emails relating to any issues in the last 3 months.
we changed server and upgraded the Redmine installation. Check your account configurations.
#5 Updated by Giovanni Manghi over 2 years ago
- Subject changed from Pasting rows from another table results in NULLs in all fields to Copy/paste features from a table in one project to another table in different project results in NULLs in all attributes
- Operating System deleted (
- Affected QGIS version changed from master to 2.18.10
- Status changed from Feedback to Open
I confirm this issue on 2.18.10, if it ever worked as expected is not recent as also 2.14.16 is affected.
Copy/pasting features between different tables within the same project works as expected.
#8 Updated by Jürgen Fischer about 1 year ago
- Resolution set to no timely feedback
- Status changed from Feedback to Closed
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.