 1 | (immediately after persist) - you have to switch to sequence or table value generation strategy. zombie |
1 |
@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "asd")
private int id |
1 | objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active' |
1 | ;
@GeneratedValue(strategy = GenerationType.SEQUENCE , generator = "gen")
@Id
private int |
1 | sequence executes when a track update comes in: - If it’s a new track simply add it to the database |
1 | please provide a test case that throws the exception. If not, we can try searching for the sequence |
1 | the SEQUENCE and TABLE strategies generate automatic values as soon as new entity objects are persisted, i |
1 | (Thread.java:662) Is this expected behavior, due to AND not being sequenced, and an attempt |
1 | (strategy=GenerationType.SEQUENCE, generator="seq")
private int gid;
@Index
private int |
1 | . For example, if you use a sequence or table - you can set an initial ID which is larger than any existing ID to avoid any conflict. gzdillon |
