About schema

151-160 of 200Refresh
Issue
1

ArrayIndexOutOfBounds on showing Tree Window

... from the Schema in ObjectDB Explorer in version 2.6.5_04 I get then the following exception (plenty of them). Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: -1 at com.objectdb.o.PEI.al(PEI.java:341) at com.objectdb.o.PEI.x(PEI.java:140) at com.objectdb.o
Forum
1

Broken @ManyToOne reference

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

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

. This may indicate a missing value, maybe as a result of schema evolution or index definition changes
Forum
1

Database size is much larger than expected (x2)

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
Forum
1

em.flush(); em.clear(); loosing data and not persisting managed objects

.persistence.Lob; import javax.persistence.Table; @Entity @Table(name = "TestEntity", schema
Issue
1

Error during closing an entity manager

that could cause it? e.g. schema change? Here is the full stacktrace: Caused by: com.objectdb.o
Issue
1

Error in production. Failed to commit transaction: Unexpected database state: BTree -152 is not found

. Have you changed the schema recently? any new index added? There are 2 different exceptions in
Issue
1

Error reading UTF string (Serialized Objects in Explorer)

the Schema tab and selecting Open Tree Window) generates a similar exception (internally) so the problem
Forum
1

Error using query with MAX() function

I have a class that is persisting a Entity that holds remarks and a time. Then when I query for the latest remark I get a internal error when the remark is larger than 1966 chars. Here is a test class and entity that reproduces the problem on my system. @Entity @Table(name = "TestEntity", schema
Issue
1

Exception upon index definition change

they may cause duplication of index values on other types of index schema upgrades. Hopefully a better fix