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
Great catch! I labelled this as a bug as I think a find should not happen. Rather an exception or actually do what's promised. Thank you, will be fixed in 6.0.10.
This changes adds support for the derived delete by supports.
To make this possible, both clients (imperative and reactive) needs to be a bit more lenient about what happens when they receive a `null` on `one`: Technically, when there has been a result but the mapping function was asked to return a `void`, this is correct.
Apart from that, the same `detach delete` logic like in `deleteById` is applied.
Valid return types for `deleteBy` are `void` or `long` or wrappers. We don’t match and return.
This closes#2281.
This changes adds support for the derived delete by supports.
To make this possible, both clients (imperative and reactive) needs to be a bit more lenient about what happens when they receive a `null` on `one`: Technically, when there has been a result but the mapping function was asked to return a `void`, this is correct.
Apart from that, the same `detach delete` logic like in `deleteById` is applied.
Valid return types for `deleteBy` are `void` or `long` or wrappers. We don’t match and return.
This closes#2281.
In Spring Data Neo4j 6.1.1 (and probably earlier), I noticed that the derived "deleteByX" queries actually don't delete; they do a find instead.
While it's easy enough to just write a custom delete query, I point this out because it's explicitly a feature in the documentation:
https://docs.spring.io/spring-data/neo4j/docs/current/reference/html/#repositories.core-concepts
Thanks!
The text was updated successfully, but these errors were encountered: