ObjectDB Database Search
51-100 of 200 resultsjakarta.persistence.OneToOne.orphanRemoval Jakarta Persistence (JPA) Method in jakarta.persistence.OneToOne boolean orphanRemoval (Optional) Whether to apply the remove operation to entities that have been removed from the relationship and to cascade the remove operation to those entities. Default: false Since: Jakarta Persistence (JPA) 2.0 | |
500Mb ObjectDb database opening issue your help in finding the exact cause of this issue. One thing you should try is to remove ... code). support Support Thank you for suggestion to remove all activation codes. I removed ... With removed activation codes 1/29/2016 18:56:00.560: INFO : (AppDataStoreManager.java:269 thread:AWT | |
jakarta.persistence.Persistence.PERSISTENCE_PROVIDER Jakarta Persistence (JPA) Field in jakarta.persistence.Persistence PERSISTENCE_PROVIDER This final String is deprecated and should be removed and is only here for TCK backward compatibility ... .spi.PersistenceProvider" or remove PERSISTENCE_PROVIDER field and also update TCK signature tests. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.EntityManager.detach(Object) Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager void detach ( Object entity ) Evict the given managed or removed entity from the persistence context, causing ... associated with this persistence context, it is ignored. Parameters: entity - a managed or removed | |
jakarta.persistence.criteria.CriteriaUpdate restrictions are simply removed . Parameters: restrictions - zero or more restriction predicates | |
jakarta.persistence.criteria.CriteriaDelete. If no restrictions are specified, any previously added restrictions are simply removed . Parameters: restrictions | |
Optimistic locking: prevent version increment on entity collection attribute the increment of the version of entity E when entities are added to or removed from the collection ... (i.e. the collection is defined as a mapped by) then adding and removing entities should not change ... side). Regarding performance, it may improve performance of adding / removing readers, but traversal from | |
Repair broken references in entities Hello, it is possible to recover an entity that has been removed automatically by CascadeType. Remove . After cascade remove the removed entity will be persisted with the identical primary key. Are all broken references in other entities on this removed /persisted entity repaired again? best regards | |
Filename.odb$ Persisting Issue Eclipse and wait a bit for it to remove itself. Any ideas why this happens? Thanks, Dragon DragonRulerX ... (); shiftImportDB.close(); emf.close(); } } I cannot/don't know how to remove external ... that this [filename].odb$ file exists for some reason (unknown to me) and doesn't always get removed | |
OneToMany and cascade delete problem over all offers from all products for given store. The problem is, that after removing product, all "connected" offers are also removed (cascade). After that, when I iterate over offers in store ... . Therefore, you must remove a Product from the list of Product instances in a Store when the Product | |
OrphanRemoval not working? { ... @ManyToOne private Invoice invoice; ... } I'm expecting, that removing invoiceitem from the list removes ... this has no effect... Is there any mistake? Thank you Michael anaq x Orphan removal was not handled ... it. Notice that usually modifications should be done on the owner side, but in the case of orphan removal | |
Slave server not getting deletes This is an interesting report. Have you tried a normal remove . i.e. not using a delete query? Update ... : Removing entity objects from the database using a DELETE query may be slightly more efficient than retrieving entity objects and then removing them, but it should be used cautiously | |
possible index required for improving query performance, putting the party first in the index definition did help. However, it did not work until I removed ... after a few thousands records were added. I'm quite happy to remove this index as we don't really need ... on one of them. Which index will it pick? 2. How do we remove this index from an existing | |
jakarta.persistence.Cache.evict(Class,Object) Jakarta Persistence (JPA) Method in jakarta.persistence.Cache void evict ( Class cls , Object primaryKey ) Remove the data for the given entity from the cache. Parameters: cls - entity class primaryKey - primary key Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Cache.evict(Class) Jakarta Persistence (JPA) Method in jakarta.persistence.Cache void evict ( Class cls ) Remove the data for entities of the specified class (and its subclasses) from the cache. Parameters: cls - entity class Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.AbstractQuery.groupBy(List) are specified, any previously added grouping expressions are simply removed . Parameters: grouping | |
jakarta.persistence.criteria.AbstractQuery.having(Predicate...) are simply removed . Parameters: restrictions - zero or more restriction predicates Returns: the modified query. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.AbstractQuery.having(List) removed . Parameters: restrictions - a list of zero or more restriction predicates Returns: the modified query. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.criteria.Subquery.where(Predicate...). If no restrictions are specified, any previously added restrictions are simply removed . This method | |
jakarta.persistence.criteria.AbstractQuery.where(Predicate...) removed . Parameters: restrictions - zero or more restriction predicates Returns: the modified query. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.Subquery.where(List). If no restrictions are specified, any previously added restrictions are simply removed . This method | |
jakarta.persistence.criteria.AbstractQuery.where(List)), if any. If no restrictions are specified, any previously added restrictions are simply removed | |
jakarta.persistence.criteria.Subquery.groupBy(Expression...) expressions are specified, any previously added grouping expressions are simply removed . This method | |
jakarta.persistence.criteria.AbstractQuery.groupBy(Expression...) expressions are specified, any previously added grouping expressions are simply removed . Parameters | |
jakarta.persistence.criteria.Subquery.groupBy(List) are specified, any previously added grouping expressions are simply removed . This method only overrides | |
jakarta.persistence.criteria.Subquery.having(Predicate...) removed . This method only overrides the return type of the corresponding AbstractQuery method. Parameters | |
jakarta.persistence.criteria.Subquery.having(List)), if any. If no restrictions are specified, any previously added restrictions are simply removed | |
jakarta.persistence.Graph.removeAttributeNode(String) Jakarta Persistence (JPA) Method in jakarta.persistence.Graph void removeAttributeNode ( String attributeName ) Remove an attribute node from the entity graph. When this graph is interpreted as a load graph, this operation suppresses inclusion of an attribute mapped for eager fetching | |
jakarta.persistence.Graph.removeAttributeNode(Attribute) Jakarta Persistence (JPA) Method in jakarta.persistence.Graph void removeAttributeNode ( Attribute attribute ) Remove an attribute node from the entity graph. When this graph is interpreted as a load graph, this operation suppresses inclusion of an attribute mapped for eager fetching | |
jakarta.persistence.Graph.removeAttributeNodes(PersistentAttributeType) Jakarta Persistence (JPA) Method in jakarta.persistence.Graph void removeAttributeNodes ( PersistentAttributeType nodeTypes ) Remove all attribute nodes of the given attribute types. When this graph is interpreted as a load graph, this operation suppresses inclusion of attributes | |
Modifying something with Explorer -> app JPQL with Enum doesn't work anymore;maintenance operations. support Support You're welcome. Well, you're asking me to remove the problem ... again. zmirc Mircea Chirac Well, you're asking me to remove the problem. The problem ... encountered this I had to remove @Enumerated with Long, and add ids for each Enum in my logic | |
Bulk Delete and Update - best practice? to update/ remove a large number of objects? I've had success with the "drop" keyword in ... found which works consistently is to load and remove objects (one by one or small batches ... of data in one transaction requires a larger heap size. This limitation may be removed in future releases | |
Schema Update: class hierarchy change/forum/899 that ObjectDB support automatic schema evolution for adding and removing fields and for class ... hierarchy ( remove field name from MyEnity) - it works (but we lost the content of field 'name ... it further? support Support Suppose we have a change, in which a class is removed from | |
Unexpected exception during open the database String scopeID; ... } if we remove the @Index annotation in the entity or we remove ... which have a field with @Index. If we remove the @Index from the entity or we remove the schema change | |
Best practice: Database update/migration of embedded databases in products. Attributes added, removed and renamed. If attributes were removed , then only because the data ... evolution - for adding and removing fields and for class hierarchy change. Configuration schema changes ... are converted and stored in the database in their new form, you can remove the fields firstName and familyName from V2.0. support Support | |
Soft Reference Object Cache Recommendation removing ObjectDB pagefile caching reference. Any help is appreciated! (P.S. Yikes!  ... all objects in a manual strong reference list and upon GC detection manually remove the strong ... Root of persistenceManager (java frame). That is right. The page cache may not be removed | |
Memory Leak in EntityManagerFactory ? and removed from memory (checked in the Profiler) 4. nevertheless there are lots of identical Copies ... (but I'll check). Should I remove the isOpen() Condition B? I will also try to call clear. The close ... ++ and close_count++ each synchronized . And in the end, there was no memory leak at all. Removing | |
Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x) and ObjectDB 2.x uses the second definition (without the index). Try to remove the second ... with that package.jdo file removed the index. So maybe after fixing the package.jdo file you will not ... is not indexed so ideally it would be using the second defination. Anyways, i tried removing the second | |
EntityManager JPA or JDO impl and different behavior path to remove the M2_REPO dependency for objectdb jar and instead add a dependency to the objectdb ... to reuse a primary key for AttributeName. So I removed the CascadeType.All from Holder and persisted ... 92 in Holder.java, and removing the persisting of OtherObject in the unit test (lines 136-139 | |
Some details about db behavior above mentioned case is persisted successfully, now I remove the A and want B to return null reference ... that when A is removed all objects referring to it will have null? I know that there are many questions ... part of the B instance. When that A instance is removed you should also update the reference from B | |
References to objects of missing obsolete entity classes: When we migrate our product profiles, we get an exception regarding entities that were removed in an earlier ... was indeed removed . This is abnormal state for a database, so if possible, is is recommended to try fixing ... deleted? or its class removed ? Was com.btc.ep.formalnotation.bl.internal.dmos.PhaseImpl | |
Improve ObjectDB Server Improve ObjectDB Server to behave and feel more like a traditional db-server: - Remove SWING dependency (i.e. remove the tray icon or make it external from the core server) - Provide the possibility to easily install the objectdb as service on each system (requires removing swing dependency | |
log entry and massive performance issues times per day we have a simple object remove (entityManager. remove ) that takes more than 5 minutes ... when the slow removal happens? It may help to identify the exact build in which this issue is started. 2 ... more information about the removed object? Is it a single object or a large graph of objects | |
again merger missing logs + objectdb exception issue rather then ObjectDB (if an object is removed from the database but still referenced ... was fixed in version 2.7.2 (temporary stack traces in the log will be removed in the next build ... that will be removed in the next build, and may be ignored now. They should be shown on any OS | |
InternalException during producer/consumer scenario objects into a table while consumer threads remove the objects based on age, priority, etc. There are 2 ... .objectdb.jpa.EMImpl. remove (EMImpl.java:377) at rbccm.felix.objectdb.messaging.ObjectDbMessagePipe ... .TYM.aq(TYM.java:840) at com.objectdb.o.TVS.g(TVS.java:93) at com.objectdb.jpa.EMImpl. remove (EMImpl | |
Blocked by find of being blocked. felixobjectdb Richard Szurgot Using find & remove seems to hit similar problems. See attached test - you can switch between delete statements and find/ remove by commenting/uncommenting ... to 8mb definitely helps the load and remove method of deleting - the test now completes when using | |
missing merger and remove the old version with missing parts. Please run the above query on the repaired database ... with later commit )? we removed all flushs and since that we do not have these errors any ... when the option in #21 is disabled. removing the option does not help hgzpincher Hans-Georg Zwicker   | |
ArrayIndexOutOfBoundsException on flush 644) at rbccm.felix.objectdb.workflow.ObjectDbGraphContainer. remove (Unknown Source) at rbccm.digest2 ... exception is a cleanup response to the first. An attempt to remove the object tree from the database ... ; em. remove (loadedgraph); em.flush();   | |
ObjectDB 2.6.5 on cascading removal of an already removed object. Renamed internal Enhancer hidden methods to non ... of connections specified in configuration. Fixed optimistic lock exception on removing of a flushed modified | |
ArrayIndexOutOfBoundException. This requires fixing the application (making sure that references to deleted objects are removed ... Sedlakova During the weekend we ran intensive tests of concurrent persist/find/ remove /update operations ... . The problem dissapeared when removing the @OneToOne(fetch = FetchType.EAGER) annotation. I am not |