55 | Inserted entities with strings as keys and indices needs more and more ram memory in comparing to primitive integers as keys and indicesHello, I have a problem with inserting of many entities. We use strings as primary key and indices. But if the db table of the entity type contains more and more data then the inserting of further entities needs also more and more ram memory, this leads to out of memory exceptions. But if use |
55 | Cannot save or update entity on Spring App methods work, there are two huge problems: the persist method does not create a new entity ... create a new entity, nor it refreshes with its new id. It is unclear from your posted code where the new entity object is instantiated but assuming that a new instance is passed to the method and not |
55 | Attempt to refresh a non managed entity object (error 635).IllegalArgumentException Attempt to refresh a non managed entity object (error 635) Nothing changed in my code ... ) on a non managed entity object, i.e. a new entity object that has not been persisted yet, or a detached entity object (e.g. after clear). It doesn't seem to be related to the IDE that you use. support |
55 | Primary key generation problem after changing entity packageHi, I changed package name for some of my entities in database. I added info in <schema><package ... . Unfortunately, sequences have been probably lost for changed entity classes. After schema change I ... (); } @Entity public static class A { @Id @SequenceGenerator(name = "SEQ |
55 | Entity object parameter in Explorer parameterHello, I cannot set an entity object in a parameter for a bulk update in the explorer query execution. The format Entity#001 works well for the parameter in the WHERE clause, but it doesn't work in ... does explorer not support an entity parameter for an update? Any time that I need to do a bulk update |
55 | How to apply constraints in collection attributes of entity.How to apply constraints like unique, not null ...etc in collection attribute of a entity. Example : @Entity @Table(name = "agent") public class Agent implements Serializable { @Id ... " should be unique through out the Entity's PhoneNumbers. Example: if a entity exist like Agent |
55 | Selective merge/cascade of detatched entity example is: @Entity public class Salesman { private String name; @OneToMany(fetch ... ; } @Entity public class Company { private String name; } For the sake of the example, each ... entity objects. To avoid multiple memory objects for the same database object you may try sharing |
55 | Populating entity id before transaction commit transaction is committed so all returned entities are not populated with ID in this context. How can I force ODB to populate entity ID before transaction is committed? Or maybe there is another way to finding ID of entity before commit? lwalkowski Lukasz Walkowski You can use a SEQUENCE (or TABLE |
11 | Incorrect entity returned by query return the expected entity. We have attached the corresponding database. The query is: SELECT dep FROM ... + dep.target.row.offsetEntry.offset > 1 We expect it to find entity 318E, however, the query returns the entity with UID: 318F. However, the returned entity does not fulfill the provided conditions |
11 | Fetch a whole entity graph eager next version ObjectDB 3.0? And do you know an easy possibility to get an entirely eager entity graph with all depended entities which we can use as a detached full accessible entity graph outside ... , we have still always the problem to get a complex completed eager entity graph. The best solution would be to provide |
