gbrodman 054c0625a8 Add SQL functionality to DeleteProberDataAction (#1218) ...

This includes a change to how the JPA transaction manager handles
existence and load checks for entities with compound IDs. Previously, we
relied on the fields all being named the same in the ID entity and the
parent entity. This didn't work for History objects (e.g. DomainHistory)
so existence checks were broken. Now, we use the methods the same way
that Hibernate does (if possible).

Note as well that there's a bit of semi-duplicated logic in
DeleteProberDataAction (between the mapper and the SQL logic). The
mapper code will be deleted once we've shifted to SQL, and for now it's
better to keep it in place for logging purposes.

2021-08-27 21:09:08 -04:00

..

gradle/dependency-locks

Implement a util class to manage push queues using Cloud Tasks API (#1290)

2021-08-24 21:13:54 -04:00

src

Add SQL functionality to DeleteProberDataAction (#1218)

2021-08-27 21:09:08 -04:00

build.gradle

Implement a util class to manage push queues using Cloud Tasks API (#1290)

2021-08-24 21:13:54 -04:00

Dockerfile

…