This is an automated email from the ASF dual-hosted git repository.
Philippus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pekko-persistence-jdbc.git
The following commit(s) were added to refs/heads/main by this push:
new a52f6b67 Update migration documentation for clarity (#627)
a52f6b67 is described below
commit a52f6b67c67c335cec97ae7244423c4444f3bfae
Author: PJ Fanning <[email protected]>
AuthorDate: Thu Sep 17 20:53:16 2026 +0100
Update migration documentation for clarity (#627)
Clarified compatibility language regarding Akka Persistence JDBC.
---
docs/src/main/paradox/migration.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/src/main/paradox/migration.md
b/docs/src/main/paradox/migration.md
index 50c5942f..73c13da5 100644
--- a/docs/src/main/paradox/migration.md
+++ b/docs/src/main/paradox/migration.md
@@ -1,7 +1,7 @@
# Migration
* If you are looking to migrate from [Akka Persistence
JDBC](https://doc.akka.io/docs/akka-persistence-jdbc/current/migration.html),
you should upgrade to 5.1.x before attempting to migrate to Pekko's equivalent.
-* If you are using a newer version of Akka Persistence JDBC, it might be best
to compare your table definitions with the Pekko table definitions of the
version of Pekko Persistence JDBC that you intend to migrate to. It is possible
that Akka have added changes that are not compatible with Pekko supports.
+* If you are using a newer version of Akka Persistence JDBC, it might be best
to compare your table definitions with the Pekko table definitions of the
version of Pekko Persistence JDBC that you intend to migrate to. It is possible
that Akka have added changes that are not compatible with what Pekko supports.
* The [Pekko Migration
Guide](https://pekko.apache.org/docs/pekko/1.0/project/migration-guides.html)
is a good summary of the changes that you need to make when switching from Akka
to Pekko.
## Migrating to 1.2.x
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
