ObjectDB ObjectDB

Internal Website Search

151-160 of 200 resultsRefresh

How to apply Unique constraints on embedded fields?

class A. Something like: @Entity @Unique(members={"b.c.values"}) @Entity public class ... you its working. but my requirement is something like this @Entity @Unique(members = { "b1.c.values ... Source) Manoj Manoj Kumar Maharana These are my sample classes. @Entity @Unique(members = { "b1

Error during cascaded merge

({     @Index(members = {"lastPosition.receiveTime"}),     @Index(members = {"lastMovingPosition ... () {         return channelConfigurationSets;     } ... } @Entity @Index(members = {"unit", "configDate

JPA query of a Set of terms

FROM SearchIndex si WHERE si.term MEMBER OF :terms",     Page.class); query.setParameter("terms ... " + "WHERE :t1 MEMBER OF p.terms AND :t2 MEMBER OF p.terms", Page.class); query.setParameter("t1", t1

Query to search for common elements in two separate collections.

I'm trying to work out the most efficient way to build a query that can compare two collections for identical members. Something like: SELECT o FROM Object o WHERE o.someCollection CONTAINS MEMBER ... . This is easier and supported by JPA: SELECT o FROM MyClass o JOIN o.someCollection e WHERE e MEMBER

Multi part paths in a composite index must have the same length

(members={"tStamp.value", "instrumentId"}) public class OBN implements Serializable{     private static ... must have the same length. Therefore, the following index definition is invalid: @Entity @Index(members ...     @Index(members={"tStamp.value", "instrumentId"})     public static class OBN {         @Id

query hint

",members={"classIdentifier","type","state","objectNameUpper"}), @Index(name="lctso",members ... "}), @Index(name="ln",members={"linkedObjects.pointingTo.nodePath"}) }) the collection is defined as

Index on map key

();     }     @Entity     @Index(members={"map.key"})     public static class MyEntity {         MyEntity(Collection ... @Index(members={"map.key"}). Running this example with and without the index definition shows that performance with index is better. support Support

LEFT JOIN FETCH over empty embedded collection returns no results

First of all, thank you for promptly implementing JOIN FETCH over nested paths in response to my inquiry a few months ago. However, I have run into one problem: if an embedded collection is empty, but I attempt to LEFT JOIN FETCH all the members of a collection within a (non-existent) member

Executing JUnit "all tests" throws "Object ... belongs to another EntityManager" Exception

the Symbol class, which has a private non-static member named string but a few static members too). I'm

Problem using "and" for joined entities and indexed fields

list. public class IndexTest {     @Entity     @Indices({         @Index(members = {"children.name"}),         @Index(members = {"children.age"})     })     static class Parent ... , which is much more efficient for the third query: @Index(members = { "children.name", "children.age" }) (with or

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