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

delete dangling feature_amounts_per_planning_unit data straight away when deleting a feature [MRXN23-518] #1647

Commits on Feb 16, 2024

  1. add test for cleanup task

    hotzevzl committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    1b7bb12 View commit details
    Browse the repository at this point in the history
  2. apply code linting

    hotzevzl committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    1084ac1 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    e47ccd8 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    fef34a0 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    8028057 View commit details
    Browse the repository at this point in the history
  6. delete dangling feature_amounts_per_planning_unit data straight away …

    …when deleting a feature
    
    This is a fast operation, so it can be done straight away. Other more
    expensive db deletions are still left to the garbage collector.
    hotzevzl committed Feb 16, 2024
    Configuration menu
    Copy the full SHA
    17ee3ea View commit details
    Browse the repository at this point in the history