ObjectDB ObjectDB

Internal Website Search

191-200 of 200 resultsRefresh
5

IN operator syntax

fine: SELECT FROM Info i WHERE i.status IN (1) The same behavior is when using MEMBER OF operator
5

Add Indexes to existing Database

Hello ObjectDB Team I might have read the solution to this issue some times before, but I could not find an answer now. So sorry for bothering you. I want do add an @Index annotation to a member of an existing Entity. This changes affects also existing databases. Is there any best practice
5

@OneToOne query issue with OR and IS NULL

is the owner. Now I persisted 2 entities of type A. In the first one, the member "another" is null... in
5

wrong query result

of fields (Content-Members) is changed alternately (48/49, 51/52), which indicates that different
5

Query performance in general

better with bigger page sizes (e.g. if an Entity has 'a lot' of member fields)? Order in WHERE clause
5

c.o.jpa.type.EntityTypeImpl.getIdType() returns null

the debugger is i can see this member m_idType is null type EntityTypeImpl<X> (id=57) m_attrMap
5

can not use spring-data-jpa repository with NamedQuery

in spring-data-jpa named queries are used to implement repository interface methods, see http://static.springsource.org/spring-data/data-jpa/docs/current/reference/html/#jpa.query-methods.named-queries for example @NamedQuery(name = "Foo.findByBar", query = "select f from Foo f where :bar member
1

@PrePersist not working correctly

I have a method to calculate some values before persisting to the database. So i annotated it with @PrePersist. If i merge an object the annotated method get's called but all members are on their default values. I only tried it with new objects. So merge get's an object with id = null
1

TYE NullPointerException

) and could not recreate the problem. I've now added a FetchType of EAGER to the member to ensure a load
1

Sort of very large objects - out of memory

    @Index(members={"priority", "createTime"})     public static class Message { If there is an index

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