ObjectDB ObjectDB

Internal Website Search

111-120 of 200 resultsRefresh
16

Internal exception when updating date filed (TemporalType.DATE)

.annotations.Index; import javax.persistence.*; public class T1312 {     public static void main(String ... ) {             try {                 entityManager.getTransaction().begin();                 for (int index = 0; index < count; index++) {                     Person person = generatePerson
16

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

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 values in that index is NULL rather than multiple values reflecting the indexed fields. This may indicate
16

JPA query of a Set of terms

SearchIndex { @Index SearchTerm term; @Index Page page; } Now suppose I have an array ... .setParameter("t1", t1).setParameter("t2", t2); By the way, since ObjectDB supports indexed collections ... Page { @Index List<SearchTerm> terms; } In that case the query is simpler (and possibly faster
16

performance limit

, what when we will have few milion records, how to handle this. Everything is set to lazy loading, we tried indexing ... range. Regards. peric.emil Emil Perić With proper indexes defined, queries on millions of objects should take only milliseconds. There could be several reasons for slow query execution, including indexes
16

Nexus proxy repository with ObjectDB

Storage Location: http://m2.objectdb.com Download Indexes, Auto Blocking, File Validation all set ... ] admin org.sonatype.nexus.index.DefaultIndexerManager - Trying to get remote index for repository ... ] admin org.sonatype.nexus.index.DefaultIndexerManager - Cannot fetch remote index for repository
14

Inserted entities with strings as keys and indices needs more and more ram memory in comparing to primitive integers as keys and indices

long types with @Index instead of string types the same advantages as primary long keys. btc_es BTC EmbeddedSystems > Have @Basic long types with @Index instead of string types the same advantages as primary long keys. The exact question is unclear. Adding additional @Index long field will not replace
14

collection of embedded objects

objects, but not always. support Support Is there any advantage to indexing collections ... A is an Entity which has a 'Set set'. I clearly need an index on B.value. Do I gain anything from an index on A.set? FastModel Ben Schreiber You cannot define an ordinary index on a field whose type
3

Database access error , Doctor hanging on trying to repair, production shutdown at our biggest customer

). Index Errors ------------ [1] Index com.agile.hummingbird.ObjectProperty[doubleValue] requires rebuild. - has 0 entries instead of 1 [2] Index com.agile.hummingbird.ObjectProperty[name] requires rebuild. - has 0 entries instead of 1 [3] Index com.agile.hummingbird.ObjectProperty[state] requires
2

Sort of very large objects - out of memory

objects. This requires a fix, but meanwhile, adding a composite index can solve the problem: @Entity     @Index(members={"priority", "createTime"})     public static class Message { If there is an index ... data (since the huge strings are excluded) the index is used by ObjectDB and query execution
0

Indices.value

Annotation Element javax.jdo.annotations.Indices Index[] value The indices Returns: The indices Since: JDO 2.1

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