 1 | locking due to a highly concurrent system that requires integrity on some value. Rest assured |
1 | that prevents this error. Integration of ObjectDB with Glassfish, especially in embedded mode, requires |
1 | was only with p2 that was defined and set but was not integrated into the query (next build will avoid a NPE in this case). Thanks, works fine... suez |
1 | it, it's more like an integration test. i try to test 4 requests in one test, but each |
1 | to ObjectDB that does not seam to be fulfilled yet: Succesfully pass JPA 2.0 TCK Referential Integrity |
1 | . Somehow the fix has not been integrated into that build. Please try build 2.6.1. PG |
1 | attribute was removed in the last version but the old XML schema validation was integrated into |
1 | to see if ObjectDB - Birt integration could be supported. ObjectDB version 2.2.7 that was just |
1 | . When using merge, the detached entity argument is used only for integrating changes. As noted |
1 | . I see two ways to integrate objectdb: first, since during 99% of the time |
