Add methods Repo.deleteByKeyVal and Repo.deleteByQuery to delete lots of rows "in place", i.e., without loading them from the database first.
Perhaps we should put these in Repo.inplace.deleteByKeyVal and Repo.inplace.deleteByQuery so as to keep the Repo API from getting too cluttered. In this picture we would have a val Repo.inplace with type InPlaceUpdates or some such. Note that in place methods updateByKeyVal and updateByQuery described in another ticket.
- Implement in all four back ends (
Cassandra, JDBC, InMem, MongoDB).
- Add integration test for
deleteByKeyVal in RepoCrudSpec.
- Add integration tests for
deleteByQuery in longevity.integration.queries. It may take a little bit of thought and discussion to come up with a minimal set of tests here to cover cases.
Add methods
Repo.deleteByKeyValandRepo.deleteByQueryto delete lots of rows "in place", i.e., without loading them from the database first.Perhaps we should put these in
Repo.inplace.deleteByKeyValandRepo.inplace.deleteByQueryso as to keep theRepoAPI from getting too cluttered. In this picture we would have aval Repo.inplacewith typeInPlaceUpdatesor some such. Note that in place methodsupdateByKeyValandupdateByQuerydescribed in another ticket.Cassandra,JDBC,InMem,MongoDB).deleteByKeyValinRepoCrudSpec.deleteByQueryinlongevity.integration.queries. It may take a little bit of thought and discussion to come up with a minimal set of tests here to cover cases.