6 | Complex Schema Upgrade not working class' table has no records either. However, looking at the DB-Size, it still has the same size? The DB |
6 | Schema-Update: Rename superclass and remove one subclass", RenamedSuperClass.class); List<RenamedSuperClass> result = q.getResultList(); System.out.println("size: " + result.size()); We get an exception: [2016-11-14 10:48:56 #1 *] java.lang.NullPointerException |
6 | Is 2 level cache in use?Hi, Is there any way to check, if 2 level cache is in use? Right now I've done two things: 1. objectdb.conf with cache size is placed in WEB-INF directory of my web application. 2. persistence.xml ... configuration by setting its size to 0. The main problem with the default implementation is that the server |
6 | Persist not working when ObjectDB and another db is used in the same application (through spring) with different tx managers").getResultList(); System.out.println(t.size()); } @Transactional(readOnly = false) public void ... ").getResultList(); System.out.println(t.size()); } pmbrierley Michael Brierley Both addObject |
6 | RT Java application recording into 100DB run OOM after a few hours. are per database. For example, the default cache size for database pages is 64GB per database, or 6.4GB per 100 databases, so it can easily exceeds your VPS RAM. If you must keep 100 databases open concurrently then you will have to reduce cache sizes, etc. support Support |
6 | List of Enum Values in an entity.toString(flags.size()); System.out.println(" Number of Flags: " + flagNumber); System.out.println ... + " (signed on " + signingDate + ")"; if (flags != null && flags.size() > 0) { for (GuestFlag |
6 | OneToMany and cascade delete problem: Store: 4, size: 10 Offer: Offer for product: 94, store: 4 Offer: Offer for product: 54, store: 4 ... test with enhancement enabled produces: Store: 4, size: 9 Offer: Offer for product: 64, store: 4 |
6 | Join performance in Objectdb of Objectdb seems to be based on the size of fields of entities: JPQL> select count(e.id) from Page e ... but then it would work faster. > The aggreiation of Objectdb seems to be based on the size of fields of entities. I |
6 | Possible issue with timestamps); List<CDI> results = query2.getResultList(); assertEquals(1, results.size ... , results.size()); assertEquals("first16", results.get(0).getFirstname |
6 | cache optimizing> <general> <temp path="$temp" threshold="64mb" /> <network inactivity-timeout="0" /> <url-history size="50 ... " /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery enabled="true" sync="true |
