GitHub user mdedetrich edited a comment on the discussion: Add new deleteObject functions to Persistence API
> But as far as > PR#[apache/pekko-persistence-jdbc#156](https://github.com/apache/pekko-persistence-jdbc/pull/156) > is concerned, it also has a different behavior of delete in 1.0. Once the PR > is merged, it will cause the possibility that the user expects to delete but > does not delete. Just wanted to point out that changing the behaviour is not out of the question as long as its warranted and ideally the breaking behaviour is more strict then the current behaviour so its easy to detect, i.e. Pekko 1.1.x [has such a breaking change ](https://pekko.apache.org/docs/pekko/snapshot/migration/migration-guide-1.0.x-1.1.x.html#splitwhen-splitafter-behavior-change) GitHub link: https://github.com/apache/pekko/discussions/1233#discussioncomment-8907818 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
