ObjectDB Database Search

;       System.out.println(results. size ());       ... ;     System.out.println(results. size ());        

has different members, but the same size .  List uid1_list = .. new Testclass(1,1), new Testclass(2,1 ... list the size of 3   To avoid this behavior (of the criteria builder.in method), you can set

that is added to my application that currently has 15 eclipse plugins. The size of objectdb.jar is 1.29 MB ( times 15 = 19.35Mb!) - a significant increase in size . With a single eclipse plugin I

system memory.  Is this size of database file supported in-memory on ObjectDB. We have a server ... supports pure memory database since version 2.6.4. There is no size limit, but it is a new feature, so if you experience issues let us know. support Support

the entitymanager I write something like vector. size () or I print it's size or I do anything with the vector

). The OutOfMemoryError crash when running the Doctor is probably due to insufficient heap size . The Doctor seems to run fine with the default JVM heap size on a PC with 16GB RAM. Did a server restart solve the issue

side in C/S mode) still keeps the changes in memory until commit. As a result, the transaction size is limited by the available JVM heap size . Actually to be able to store 1GB of data in a single

Hi Team, We are observing an Out of Memory error while accessing odb files, but it occurs inconsistently. The sizes of the odb files are not large, with a maximum of 4-5MB. Please see the attached ... , Vinoth vinothr120 Vinoth Ramesh OutOfMemoryError is expected when the heap size is insufficient

. that seems reasonable 1. Our server does (minimum) one database-file backup per day and the size may be in between 100 MB to 1GB (without documents) which means the size of the backup directory will increase

.getName()));     criteria.where(predicates.toArray(new Predicate[predicates. size ... Predicate[predicates. size ()])); return em.createQuery(criteria).getSingleResult();   String queryStr

Harman company requested to reduce ODB size as much as possible after database created and one of unliked solution was to use ZIP/UNZIP after/before use object DB database. Harman would like to ask ... ODB size up to 50 times. Additional info: https://www.objectdb.com/issue/23 Harman Alexander Golyshkin

Size : Our MySQL database was 66GB in size before migration. Migration Status : We are halfway

.getResultList(); assertTrue(firstQueryResult. size () == 1); EntityManager innerEm = emf.createEntityManager ... (); assertTrue(secondQueryResult. size () == 2); assertTrue(secondQueryResult.get(0).strValue != null

well, so, the TreeSet is reduced in size ? Or do I end up having a number of null pointers in the Sets? 

to the server. Possible directions you may consider: Increasing the size of the connection pool to reduce

more information about the database health a. Show actual running values for all parameters in objectdb.conf ( size

Font size on new site is huge! This is especially a problem when browsing the api.   dmoshal David Moshal Difficult to find info on ODB1, including api javadocs. dmoshal David Moshal Thank you for your useful comments. The ObjectDB 1 manual is available here . You can use the JDO menu

usage threshold. If you have sufficient RAM try to increase the threshold. Regarding the size

) to the database is expected to take much more time than persisting one large object of the same total size

to run the query from  https://www.objectdb.com/forum/2845  (database size 20GB

, rather than relying on one- size -fits-all EAGER. This pre-detach loader approach is even more flexible

= query7.getResultList(); assertEquals(1, q7results. size ()); It looks like the result is not filtered

@Inheritance(strategy=InheritanceType.JOINED) // Success for Inheritance Sonsection //@Cache( size =10000

a connection). By default the maximum connection pool size is 50. You can change it in the persistence

we cannot explore issues in projects of this size . support Support Okay, here is a only main class project

;     Size         

collection. ObjectDB surely has some idea of the sizes of objects that it persists and retrieves

.getResultList(). size ());              

but then it would work faster. The aggreiation of Objectdb seems to be based on the size of fields

: departments) em.remove(d); em.getTransaction().commit(); }while(departments. size () 0); }catch

which is 3G in size and I think half of it was converted. The output is much longer (see it in attachment

(Thread.java:833) I was also checking the used heap size chart in JConsole while my test case caused

): We create a 1G DB file when the application starts for the fist time. The size of the DB file does not

INNER JOIN c.addresses ORDER BY SIZE (c.addresses) 0 ? CONCAT(c.addresses[0].street + c.addresses[1

: The element - try reducing the number of threads and the cache size (notice that this setting

Our application has some complex entities. We do batch update(merge detached entity) every 2 minutes. We find the period significant IO costs these days, and disappeared when turn off the batch updating. 1.ObjectDB is in embedded mode. 2.ObjectDB version is 2.3.7 3.Database file size is nearly

;    System.out.println(resultList. size ());        

.util.TreeSet.__odbBeforeAccess(Unknown Source) at objectdb.java.util.TreeSet. size (Unknown Source

when the operation has started). You cannot disable that cache since it has a minimum size even if you request zero size . In some situations (e.g. when using flush that is followed by other operations and then commit

Extended maximum supported entity object size to nearly 2GB. Added a temporary system property to disable "enhancement ... is old" checks. Fixed a bug in handling remove and persist of the same ... property access mode. Fixed a bug in allowing page sizes larger than 64KB (which are not supported by ObjectDB). Fixed an issue of very slow online backup.

in which ObjectDB does not have enough heap space. Please try to increase the size of the JVM heap or change the configuration to use less heap size . support Support

size . We did not configure a log-archive (log-archive path="" retain="0"). That caused an exception when the log file reached its size limit. Here's the stack trace of that issue: com.objectdb.o

cached query result size . Since Java doesn't provide information on heap memory size of data

We are testing client-server architecture. Our server has the following config: path = "$temp" threshold = "64mb" / inactivity-timeout = "0" / size = "0" user = "true" password = "true" / path ... = "0" /                 size = "0" user = "true" password

Improved performance of collection and map size evaluation in queries. Fixed a critical bug in page caching (issues #610 , #621 , #625 ). Fixed a bug in optimization of non ASCII string indexes. Fixed the new query HOUR function to return hours as 0 to 23 (using 24-hour clock). Fixed a regression

Fixed a bug in using SIZE on byte[] in queries.

size (-Xmx1024m may not be sufficient). support Support Do you still see this error message

.class, 1l);   Assert.assertEquals(0, parentEntity.getChildEntityContainer(). size ());  

file size = 297009152, dirty pages = 1, update list s = 2, dirty page map = 1,   FastModel Ben

Hi   there is something wrong with enhancement process I got that class was succesfully processed, log has size 0, enhancer is from build objectdb-2.2.8_08 and during object creation when some filed is initialised i got an exception   Exception in thread "main" java.lang.NoSuchFieldError