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
Copy file name to clipboardExpand all lines: README.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,14 +11,15 @@ Focus is the usage with spring boot and JPA.
11
11
Secondary goal is to support [Poor mans Workflow](https://github.com/sterlp/pmw)
12
12
13
13
# Key Features ✨
14
+
14
15
1.**JPA-Powered Persistence** - Automatically persists tasks to your database
15
16
1.**Spring Boot Auto-Configuration** - Simple setup with @EnableSpringPersistentTasks
16
17
1.**Clustering Support** - Built-in lock management for distributed environments
17
18
1.**Type-Safe Tasks** - Generic task definitions with state objects
18
19
1.**Retry Mechanisms** - Automatic retry policies for failed executions
19
20
1.**Transactional Integration** - Works with Spring's transaction management
20
21
1.**Queue Management** - Intelligent task queuing and prioritization
21
-
1.**Different DB Supports** --
22
+
1.**Different DB Supports** - MySQL, azure-sql-edge, PostgreSQL, and H2
22
23
23
24
# Documentation
24
25
@@ -27,25 +28,25 @@ The README contains a shorter how to use.
27
28
28
29
# Known issues
29
30
30
-
- spring-boot-devtools: cause java.lang.ClassCastException exceptions during the state serialization - this is a java/spring issue
31
+
-spring-boot-devtools: cause java.lang.ClassCastException exceptions during the state serialization - this is a java/spring issue
31
32
32
33
# Known limitations
33
34
34
35
## DBMS have missing bad row lock implementation
35
36
36
37
The framework briefly locks a row or trigger to ensure that each trigger is started only on a single node when a cluster is in use. However, some databases still do not support proper row locking and instead lock the entire table. This is not a critical issue but can slow down task selection in very large clusters.
0 commit comments