Skip to content
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

values for cached join fields randomely become null when dragging canvas #25347

Closed
qgib opened this issue Nov 14, 2017 · 6 comments
Closed

values for cached join fields randomely become null when dragging canvas #25347

qgib opened this issue Nov 14, 2017 · 6 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Regression Something which used to work, but doesn't anymore Vectors Related to general vector layer handling (not specific data formats)

Comments

@qgib
Copy link
Contributor

qgib commented Nov 14, 2017

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)
Original Redmine Issue: 17450
Affected QGIS version: master
Redmine category:vectors
Assignee: Paul Blottiere


I've finally been able to reduce this features going missing issue that's been haunting me for a while now.

When doing multiple joins like this: ```i.e. fields ORIGINAL -> joined fields A linked through a field in ORIGINAL -> joined fields B linked through a joined field in A


*Steps to reproduce*
1. Open the attached join_cache test project
1. When the project opens, start rapidly panning the canvas around (small steps using the mouse's middle button is the easiest way)
1. You'll notice the dark pink polygons going missing after every few pans (see gonebabygone.mp4 video too)

This does not only affect feature rendering, saving the layer (with all its joins) can actually write null values for joined fields B.

---

- [join_cache_issue.zip](https://issues.qgis.org/attachments/download/11677/join_cache_issue.zip) (Mathieu Pellerin - nIRV)
- [gonebabygone.mp4](https://issues.qgis.org/attachments/download/11678/gonebabygone.mp4) (Mathieu Pellerin - nIRV)
- [gonebabygone.mp4](https://issues.qgis.org/attachments/download/11679/gonebabygone.mp4) (Mathieu Pellerin - nIRV)
@qgib
Copy link
Contributor Author

qgib commented Nov 14, 2017

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)


  • description was changed from I've finally been able to reduce this features going missing issue that's been haunting me for a while now.

When doing multiple joins (

i.e. fields ORIGINAL -> joined fields A linked through a field in ORIGINAL -> joined fields B linked through a joined field in A
), the values can get lost if the joins are cached.

Steps to reproduce

Open the attached join_cache test project

When the project opens, start rapidly panning the canvas around (small steps using the mouse's middle button is the easiest way)

You'll notice the dark pink polygons going missing after every few pans (see gonebabygone.mp4 video too)

This does not only affect feature rendering, saving the layer (with all its joins) can actually write null values for joined fields B. to I've finally been able to reduce this features going missing issue that's been haunting me for a while now.

When doing multiple joins like this:

i.e. fields ORIGINAL -> joined fields A linked through a field in ORIGINAL -> joined fields B linked through a joined field in A
the values will get lost every now and then when those joins are cached.

Steps to reproduce

Open the attached join_cache test project

When the project opens, start rapidly panning the canvas around (small steps using the mouse's middle button is the easiest way)

You'll notice the dark pink polygons going missing after every few pans (see gonebabygone.mp4 video too)

This does not only affect feature rendering, saving the layer (with all its joins) can actually write null values for joined fields B.

@qgib
Copy link
Contributor Author

qgib commented Nov 14, 2017

Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)


Better video, featuring the reduced test project attached.


  • 11679 was configured as gonebabygone.mp4

@qgib
Copy link
Contributor Author

qgib commented Nov 14, 2017

Author Name: Giovanni Manghi (@gioman)


Seems also to not happen in 2.18(?).


  • regression was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Nov 15, 2017

Author Name: Paul Blottiere (Paul Blottiere)


  • assigned_to_id was configured as Paul Blottiere

@qgib
Copy link
Contributor Author

qgib commented Nov 15, 2017

Author Name: Regis Haubourg (@haubourg)


PR proposed here [[https://github.com//pull/5638]]

@qgib
Copy link
Contributor Author

qgib commented Nov 22, 2017

Author Name: Paul Blottiere (Paul Blottiere)


Applied in changeset 333a8e9.


  • done_ratio was changed from 0 to 100
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Nov 22, 2017
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Vectors Related to general vector layer handling (not specific data formats) Crash/Data Corruption Regression Something which used to work, but doesn't anymore labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption High Priority Regression Something which used to work, but doesn't anymore Vectors Related to general vector layer handling (not specific data formats)
Projects
None yet
Development

No branches or pull requests

1 participant