ObjectDB ObjectDB

Internal Website Search

111-120 of 158 resultsRefresh
8

Some details about db behavior

me with this please link them. Regards vachagan Vachagan If A is an entity class (and not an embeddable class ... ), you should see an A instance in the database. If A is an embeddable class the content of A will be persisted as
8

Searching lists within objects

ArrayList<Attribute>(); } @Embeddable class Attribute {     private AttributeType type ... embeddable objects for the search. However, I am not sure if indexes are currently used in
8

Navigation through Path to evaluate collection

and the related embeddable class. Thanks public synchronized List<ProductData> getList(String key ... ; } @Embeddable public class ApiIdData_ implements Serializable {         private String apiName
8

Pre-detach loading: retrieval by navigation not working in if statement

wrapper rather than embeddable class, which could be more efficient (and as a bonus will also eliminate ... wrapper rather than embeddable class, > which could be more efficient (and as a bonus will also eliminate
8

Is named-query supported in orm.xml

":entity, "http://java.sun.com/xml/ns/persistence/orm":embeddable}' is expected. Does ObjectDB support ... queries should be defined in the XML before any type (entity, embeddable, etc.) definition. Named queries
8

Suggestion for improving the examples

: Take the ridiculously complicated concept of @Embeddable class e.g Address etc... Placed in an employee ... and when embeddable classes are introduced we prefer to focus on that topic only with minimal code that is needed
8

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

Support On a side note, in your model PersonalData in defined as an embeddable class ... field. To avoid data duplication consider using Entity instead of Embeddable for this type. support Support
5

Database size is much larger than expected (x2)

levels of the hierarchy), or by including it in an embeddable object that is references twice
5

persistence.xml classes not respected by ObjectDB

Hi! I have the following persistence.xml. The problem is that ObjectDB loads all the classes in P1 (+ their embeddable classes). P2 is created properly, but P1 gets all entity classes (from P2 also). How can this be avoided, so that both P1 and P2 get just the classes that were specified to each
1

ObjectDB 2.6.5

querying enhanced embeddable classes. Fixed server crash on exceeding maximum number of connections

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