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

[WIP] Separate symbology and labels from od #509

Draft
wants to merge 71 commits into
base: main
Choose a base branch
from

Conversation

cymed
Copy link
Contributor

@cymed cymed commented Dec 17, 2024

General

  • Fix a bug
  • Add a feature
  • Maintenance / sustainability
  • Add Documentation

Describe your changes

Concept of #409, but including symbology.

The PR introduces

  • a table tww_od.tww_symbology_quarantine
  • a table tww_od.tww_reach_point_labels
  • a table tww_od.tww_wastewater_structure_labels
  • a table tww_od.tww_wastewater_node_symbology
  • a view tww_app.vw_tww_wastewater_node to include the now separated symbology columns. TODO: currently, moving the vw_tww_wastewater_node moves the corresponding reaches/reach points as well. Is this behaviour desired?

Changes on symbology are now stored in a separate table, which in turn leads to fewer circular triggers.
The symbology triggers now only add the wastewater structure/wastewater node OID to tww_od.tww_symbology_quarantine. After an INSERT, a statement level trigger updates symbology and labels

To-Do

When altering a geometry in tww_app.vw_tww_wastewater_node, the geometry of the reaches/reach points linked to it are updated too. We need feedback from the user group if this behaviour is desired or not.

Screenshots

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • If it is a core feature, I have added thorough tests.
  • CI Tests are green
  • The documentation is up to date with the proposed change.
  • My work is ready for review

Checklist before merge

  • A review has been performed
  • Comments are resolved
  • Documentation is ready

@cymed cymed added enhancement New feature or request datamodel Concerns the datamodel app_schema Concerns the application schema labels Dec 17, 2024
@cymed cymed modified the milestones: TEKSI Wastewater 2024.1, Future Dec 20, 2024
@cymed
Copy link
Contributor Author

cymed commented Jan 7, 2025

I am struggling with the tests: As the label triggers are now deferred, we need to commit the transaction before testing labels and symbologies. When exactly should I commit and will committing impact the other tests?

@cymed cymed added help wanted Extra attention is needed and removed review Waiting for review labels Jan 7, 2025
@cymed cymed self-assigned this Jan 15, 2025
@cymed cymed marked this pull request as draft January 15, 2025 07:59
@cymed cymed modified the milestones: Future, TEKSI Wastewater 2025.0 Jan 15, 2025
@sjib
Copy link
Contributor

sjib commented Feb 24, 2025

@cymed could you describe how the new _status (integer) attribute should work?

What is the reason to remove the attributes tww_active and tww_local_extension?

@cymed
Copy link
Contributor Author

cymed commented Feb 24, 2025

@cymed could you describe how the new _status (integer) attribute should work?

_status is not new, it already exists on wastewater_node

What is the reason to remove the attributes tww_active and tww_local_extension?

They were in the code twice, I removed one entity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app_schema Concerns the application schema datamodel Concerns the datamodel enhancement New feature or request help wanted Extra attention is needed QGIS project Concern the .qgs QGIS project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Symbology performance improvements
3 participants