ObjectDB Database Search

versions of the same entity are in use? If so, this could cause the schema to be repeatedly detected

with ordinary objects. Fixed a schema evolution bug when adding a new super entity class .   support Support

I store images into objectdb. The schema is : ::=( , , , , ) ::=String ::=char ::=int ::=byte[] ::=@ID So simple a class will fail after 155,648 insertions with -Xmx1432m, ... NO = 151552 @ 8042217472 id = 0 @ 7703244276 Url = http://cimg2.163.com/catchpic/E/E9/E96492634557CE291CDF3AADC710F373.jpg

after schema change. After adding an index to an existing entity class with instances in the database

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

the classpath, the Explorer uses the schema as defined in the odb file). Please try to remember

nothing whether such situations are allowed or forbidden. Unfortunately, in my schema the child id

a critical database corruption bug ( issue #187 ). Fixed a critical bug in schema evolution

classes are involved?  CacheableJobStat ? CacheableJobLog ? Could you describe their schema

the Schema / Managed Types list and then deleted by using [Edit Delete] from the menu bar or right click (context menu) and Delete. support Support

of this type in the explorer (by right clicking the type in the Schema tab and selecting Open Tree

) it may help identifying a pattern and finding a solution. If the schema and indexes are the same

; longpat Brian O'Hare Maybe the server was still running. Schema changes  requires server restart . I

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

reports.) CBE CBE In case it helps you (because 2.7.2_05 release notes state "Fixed a bug in schema