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
{{ message }}
This repository was archived by the owner on Mar 20, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,25 +29,27 @@ Both journal and snapshot store share the same configuration keys (however they
29
29
-`class` (string with fully qualified type name) - determines class to be used as a persistent journal. Default: *Akka.Persistence.PostgreSql.Journal.PostgreSqlJournal, Akka.Persistence.PostgreSql* (for journal) and *Akka.Persistence.PostgreSql.Snapshot.PostgreSqlSnapshotStore, Akka.Persistence.PostgreSql* (for snapshot store).
30
30
-`plugin-dispatcher` (string with configuration path) - describes a message dispatcher for persistent journal. Default: *akka.actor.default-dispatcher*
31
31
-`connection-string` - connection string used to access PostgreSql database. Default: *none*.
32
+
-`connection-string-name` - in case when connection-string is empty, this field specifies entry in the \*.config connection string section, from where connection string will be taken. Default: *none*.
-`schema-name` - name of the database schema, where journal or snapshot store tables should be placed. Default: *public*
34
35
-`table-name` - name of the table used by either journal or snapshot store. Default: *event_journal* (for journal) or *snapshot_store* (for snapshot store)
35
36
-`auto-initialize` - flag determining if journal or snapshot store related tables should by automatically created when they have not been found in connected database. Default: *false*
37
+
-`timestamp-provider` (journal only) - type of the object used to generate journal event timestamps. Default: *Akka.Persistence.Sql.Common.Journal.DefaultTimestampProvider, Akka.Persistence.Sql.Common*
36
38
37
39
### Custom SQL data queries
38
40
39
41
PostgreSql persistence plugin defines a default table schema used for both journal and snapshot store.
@@ -59,9 +61,9 @@ PostgreSql persistence plugin defines a default table schema used for both journ
59
61
Underneath Akka.Persistence.PostgreSql uses the Npgsql library to communicate with the database. You may choose not to use a dedicated built in ones, but to create your own being better fit for your use case. To do so, you have to create your own versions of `IJournalQueryBuilder` and `IJournalQueryMapper` (for custom journals) or `ISnapshotQueryBuilder` and `ISnapshotQueryMapper` (for custom snapshot store) and then attach inside journal, just like in the example below:
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,16 @@
1
1
#### 1.0.5 August 08 2015 ####
2
2
3
+
- Changed tables schema: renamed payload_type column to manifest for journal and snapshot tables
4
+
- Changed tables schema: added created_at column to journal table
5
+
- Added compatibility with Persistent queries API
6
+
- Added ability to specify connection string stored in \*.config files
7
+
3
8
#### 1.0.4 August 07 2015 ####
4
9
5
10
#### 1.0.3 June 12 2015 ####
6
11
**Bugfix release for Akka.NET v1.0.2.**
7
12
8
-
This release addresses an issue with Akka.Persistence.SqlServer and Akka.Persistence.PostgreSql where both packages were missing a reference to Akka.Persistence.Sql.Common.
13
+
This release addresses an issue with Akka.Persistence.SqlServer and Akka.Persistence.PostgreSql where both packages were missing a reference to Akka.Persistence.Sql.Common.
9
14
10
15
In Akka.NET v1.0.3 we've packaged Akka.Persistence.Sql.Common into its own NuGet package and referenced it in the affected packages.
0 commit comments