dahn be255e4203

server: protect against stray snapshot-details without snapshot (#4924) ...

This PR makes sure no orphaned snapshot details are considered in the cleanup at startup job.
a real solution would be to implement some kind of cascading delete, but as the parent record is "only" marked as removed this would be a bit com

Co-authored-by: Daan Hoogland <dahn@onecht.net>

2021-04-29 20:40:29 +05:30

..

agent-lb

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

ca

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

cluster

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

config

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

db

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

direct-download

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

events

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

ipc

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

jobs

server: protect against stray snapshot-details without snapshot (#4924)

2021-04-29 20:40:29 +05:30

managed-context

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

quota

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

rest

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

security

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

spring

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30

pom.xml

Updating pom.xml version numbers for release 4.15.1.0-SNAPSHOT

2021-01-11 13:58:30 +05:30