ObjectDB ObjectDB

Internal Website Search

151-160 of 200 resultsRefresh

Removing an entity throws exception

mainly to detected changes when enhancement is not in use) - after schema evolution. Therefore, starting with a new database file could solve the problem even with no fix, since the schema changes

Query results are not up to date for entities, not primitives

arrays="false" /> </entities> <schema> </schema> <server>   <connection port="6136" max="100

Is named-query supported in orm.xml

against the JPA 2 ORM schema, probably because of the location of the named-query element in the XML file. Maybe EclipseLink is more flexible and doesn't enforce the formal schema. Global named

Replication Issue

" />         </entities>         <schema>         </schema>         <server>                 <connection

Degrading performance overtime

" /> </entities> <schema> </schema> <server> <connection port="6136" max="100" /> <data path

InternalException & UserException using objectdb with Jboss AS 7.1.1 final

database or after applying schema change. If you get this exceptions only with a new database

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: 2

to use a new class schema, which the client is unaware to yet. The ObjectDB server must be restarted after a schema change. Do you still get the error after restarting the server? support Support

Unable to stop server after starting in SSL mode

="false" /> </entities> <schema> </schema> <server> <connection port="xxxx" max="100

stress test -> com.objectdb.o.InternalException: null

is to separate building the schema (i.e. registration of all the managed types) from the load test, i.e ... , and there is no redeployment or schema modification happening. Tomee is started (with the already deployed app

InternalException - error reading field from "queue" database

the _payload field. It contains instances of an unknown type whose schema is not stored in the database, i ... to the other reported problem of inability to update the schema in a replicated database

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