 1 | The JPQL (Java Persistence Query Language) supports defining subqueries, which are nested queries that are embedded in other queries. Subqueries are currently not supported by ObjectDB, and as a workaround, you can use a sequence of two or more queries, where the results of one query serves as |
1 | We had a database failure causing a production outage. Both master and slave databases have failed, slave became unresponsive and the master switched to read-only mode. By the look of it the slave database failed first and possibly caused the master to switch to read-only mode. The sequence |
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 |