ObjectDB ObjectDB

Internal Website Search

91-100 of 165 resultsRefresh

how explorer queries work

to build missing entity and embeddable classes, based on the schema that is internally stored in ... defined serializable non entity / embeddable classes (which are not recommended anyway) and use embeddable classes instead. This way ObjectDB will be able to complete your missing classes. support Support

Exception when querying Map property with @embedded & Enhancer enabled

MyEntity2 Thanks import java.util.LinkedHashMap; import javax.persistence.Embeddable; import javax ... + "]";   } } @Embeddable public static class MyAttributeItem {   private String id;   private String name ... embeddable classes in queries. Please try build 2.6.4_06 that should fix this issue. support Support

Changing existing objects from Entity to Embedded

(entity classes) or embeddable. To use embedded objects you must declare classes as embeddable (rather than the reference fields as in ObjectDB 1.0), either by annotation (@Embeddable) or by external XML

Problem with entities detection

. The only difference is an @Embeddable annotion in a class, and an @Embedded annotation in another. The problem ... ) and objectdb.Direccion (the @Embeddable) to the same package of centroController, it just works ... ; And this is the Embedded class: @Embeddable public class Direccion implements Serializable

Index on map key

();         }     }         @Embeddable     public static class MyEntry {         String key;         String value ... <MyEntry>, i.e. a collection of a key-value embeddable objects. An index on the key is defined using

LEFT JOIN FETCH over empty embedded collection returns no results

my original post: @Embeddable class A { String val; }; @Embeddable class B { List<A> aList

Join query problem with new statetment

an embeddable class to entity class, which results in having a class with mixed objects in the database - the old embeddable objects and the new entity objects. For more precise diagnosis - please post

Embedding Managed Entities in Embedded Objects = bad idea

Discovered that you can't embed entities in embeddable objects if the entity is managed. Haven't tried embedding un-managed entities in embeddable objects, though I imagine that's not a great idea. The the error message isn't all that obvious (attempting to persist object which already has an id

Performance in SELECT statement

... } @Embeddable public class State {     private Long lastProcessingDate;     private int ... directly on a field of embeddable class. Define a path index on TestEntity instead: @Entity @Index

New to Product & Having An Issue

.... @Embeddable @Access(AccessType.PROPERTY) public class DomainId implements Serializable { public ... classes and embeddable classes) can be compared by using the equality operators (=, <>, ==, !=). Note

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support