Internal Website Search

191-200 of 200 resultsRefresh

failure to enforce NOT NULL for java.lang.String

am certain a schema change is taking effect. running `mvn test` twice in a row without a clean between

Queries are slow on a large database

that the new schema is available. Otherwise, you may generate a new database but with the old indexes

Modifying something with Explorer -> app JPQL with Enum doesn't work anymore

with no classes in the classpath, the Explorer uses the schema as defined in the odb file).

Broken @ManyToOne reference

my schema the child id must be composed from the parent Id and the child subkey. And I have multiple

ObjectDB version 2.2 has been released

a critical bug in schema evolution of modified ancestor classes. Fixed a bug in

Is persistence version 2.1 supported?

schema .. --> <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence

Collection update does not increase entity version and is not persisted

of an old schema, in which the collection was not exist yet (as of changing

ObjectDB 2.7.2_x Doctor Yields "Index Requires Rebuild" Always

_05 release notes state "Fixed a bug in schema evolution of indexes.") ... I can confirm

ObjectDB 2.2.0

> Fixed a critical bug in schema evolution of modified ancestor classes. Fixed

ObjectDB 2.3.5

parameters display in the Explorer schema window. Fixed merging a new entity object with application set primary key.