You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first has two arguments: UpdateClause and key value. See Repo.retrieve for how to properly constrain the type of the key value. See how Query is constrained in Repo.queryBy* methods to see how to constrain the UpdateClause.
The second has two arguments: UpdateClause and Query.
Make it so! Examine how query objects are translated into mongo queries in MongoQuery to get some ideas on how to form the update clause.
You should probably write an implementation for InMem back end at the same time; It won't be that hard.
Attempting these operations on a JDBC or Cassandra back end can just throw exception for now.
Add an integration test for updateByKeyVal in RepoCrudSpec. It should avoid running if the back end is not supported.
Add integration tests for updateByQuery in longevity.integration.queries. How to design the tests and just how many we need to cover cases will require some thought. Please try to keep reasonably minimal because these kinds of tests are expensive.
The text was updated successfully, but these errors were encountered:
Implement
Repo.inplace.updateByKeyVal
andRepo.inplace.updateByQuery
to do updates "in place", or on the database.Repo.inplace
UpdateClause
and key value. SeeRepo.retrieve
for how to properly constrain the type of the key value. See howQuery
is constrained inRepo.queryBy*
methods to see how to constrain theUpdateClause
.UpdateClause
andQuery
.MongoQuery
to get some ideas on how to form the update clause.InMem
back end at the same time; It won't be that hard.JDBC
orCassandra
back end can just throw exception for now.updateByKeyVal
inRepoCrudSpec
. It should avoid running if the back end is not supported.updateByQuery
inlongevity.integration.queries
. How to design the tests and just how many we need to cover cases will require some thought. Please try to keep reasonably minimal because these kinds of tests are expensive.The text was updated successfully, but these errors were encountered: