About composite

issue

Sort of very large objects - out of memory

The attached test is failing with an out of memory exception when running with -Xmx512m It performs the following actions: 1) Create 5 persist threads which create and persist a large object in a loop 100 times each 2) Create 5 get threads which read 100 objects each in a loop based on object creation time and priority The message size should be around 1mb so I think there should be around 11mb of "live" data in play at any time. The objectdb cache settings are low in the config - database section is below for reference. ... objects. This requires a fix, but meanwhile, adding a composite index can solve the problem: @ Entity @ ... range query could just pick the first or last entry in the composite index (instead of scanning the entire index). Composite ...

 
release

2.3.4

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
release

2.5.1

... Improved evaluation of query plans that use composite indexes . Improved processing of queries with a large ... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ...

 
release

2.3.6

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
release

2.3.1

... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
release

2.3.5

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
manual

Database Replication and Clustering

Replication enables maintaining up to date version of an ObjectDB database on multiple nodes.... rather than on the master server. Finally, a composite url can also be used: EntityManagerFactory emf = ... ) ; A composite url contains two or more database urls separated by '|' . ...

 
forum_thread

Broken @ManyToOne reference

Hi, I have objects of type A belonging to objects of type B, defined as follows: @MappedSuperclass public abstract class A {   @Id   @ManyToOne(fetch = FetchType.EAGER, cascade=CascadeType.ALL, optional=false)   private B b;   @Id   @Column(length = 36)   private String stringId; } @MappedSuperclass public abstract class B {   @Id   private String name; } ... just tried the fixed version. Two notes: 1. For a composite key an instance of the target class may be used. At least it works ... You should use an  ID class to represent composite primary keys in a portable JPA way. ObjectDB ...

 
release

2.3.7

... and NullPointerException in using a composite index in queries ( issue #74 ). Fixed Explorer bugs: ... ). Fixed a ClassCastException in using a composite index in queries ( issue #71 ). Fixed handling derived Id fields in composite PK embedded IDs. Fixed default ObjectDB home path ( ...

 
forum_thread

com.objectdb.o.NLV cannot be cast to com.objectdb.o.CMV

We are using ObjectDB 2.5.1_04. The following JPQL query causes an internal exception: SELECT COUNT(r) FROM RecordingMetaData AS r WHERE ((r.mapFromCli LIKE '192.168.10.13%' ESCAPE '\')) The exception: ... It seems that the query is executed using a composite index on the  mapFromCli field. Could you please provide details on composite indexes that include that field? Unexpectedly, one of the ...