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

DB Manager: previewing layers in Virtual layers section remove them from the Layers panel #24385

Closed
qgib opened this issue Apr 27, 2017 · 11 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption DB Manager Relating to the DB Manager core plugin High Priority

Comments

@qgib
Copy link
Contributor

qgib commented Apr 27, 2017

Author Name: Harrissou Santanna (@DelazJ)
Original Redmine Issue: 16476
Affected QGIS version: master
Redmine category:db_manager


Open a project
Launch DB Manager, expand the Virtual layers section, then QGIs layers and select a layer
Click the Preview tab
Select another layer
The layer you selected first has been removed from the Layers panel, hence from the project (GUI, at least)

Happens also in master
Set the report as high because this can easily corrupt the project if you don't notice the removal (and anyway, if you notice it, you'll need to close and not save the project to avoid it being corrupted)


Related issue(s): #24440 (duplicates)
Redmine related issue(s): 16534


@qgib
Copy link
Contributor Author

qgib commented Apr 27, 2017

Author Name: Harrissou Santanna (@DelazJ)


  • subject was changed from DB Manager: previewing layers remove them from the Layers panel to DB Manager: previewing layers in Virtual layers section remove them from the Layers panel

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented May 1, 2017

Author Name: Giovanni Manghi (@gioman)


  • description was changed from Open a project
    Launch DB Manager, expand the Virtual layers section, then QGIs layers and select a layer
    Click the Preview tab
    Select another layer
    The layer you selected first has been removed from the Layers panel, hence from the project (GUI, at least)

Happens also in master
Set the report as high because this can easily corrupt the project if you don't notice the removal (and anyway, if you notice it, you'll need to close and not save the project to avoid it being corrupted) to Open a project
Launch DB Manager, expand the Virtual layers section, then QGIs layers and select a layer
Click the Preview tab
Select another layer
The layer you selected first has been removed from the Layers panel, hence from the project (GUI, at least)

Happens also in master
Set the report as high because this can easily corrupt the project if you don't notice the removal (and anyway, if you notice it, you'll need to close and not save the project to avoid it being corrupted)

  • crashes_corrupts_data was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented May 10, 2017

Author Name: Luigi Pirelli (@luipir)


the problem is a logic problem... the db_manager base class layer_preview remove from registry any previously added layer (currentLayer) with it's id, with assumption that it's id is a temporary layer because has been added for the preview.

virtual layer qgis layer is populated of all registry layers => also that are in the layer list, when you click on that it become current layer => it is removed when switching to another layer in db_manager

looking for a simple solution for that

@qgib
Copy link
Contributor Author

qgib commented May 10, 2017

Author Name: Giovanni Manghi (@gioman)


see also #24440

@qgib
Copy link
Contributor Author

qgib commented May 12, 2017

Author Name: Luigi Pirelli (@luipir)


fixed for 2.18 #4534 waiting for review and merge, expecially review by Hugo Mercier.
fix for 3.0 will be delayed because actually in this version db_manager raise much more exception than the 2.18 or 2.14 one => I'll try to work in a general PR fixup most common one.


  • pull_request_patch_supplied was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented May 19, 2017

Author Name: Jürgen Fischer (@jef-n)


@qgib
Copy link
Contributor Author

qgib commented May 28, 2017

Author Name: Salvatore Larosa (@slarosa)


Applied in changeset dae921c.


  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Feb 2, 2018

Author Name: Harrissou Santanna (@DelazJ)


Looks like the fix for QGIS 3 never landed


  • status_id was changed from Closed to Reopened
  • version was changed from 2.18.7 to master

@qgib
Copy link
Contributor Author

qgib commented Feb 3, 2018

Author Name: Salvatore Larosa (@slarosa)


Applied in changeset 68b7bf6.


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

@qgib qgib closed this as completed Feb 3, 2018
@qgib
Copy link
Contributor Author

qgib commented Feb 22, 2018

Author Name: Giovanni Manghi (@gioman)


  • resolution was changed from to fixed/implemented

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority DB Manager Relating to the DB Manager core plugin Crash/Data Corruption 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 DB Manager Relating to the DB Manager core plugin High Priority
Projects
None yet
Development

No branches or pull requests

1 participant