ObjectDB Database Search
51-100 of 200 resultsSignificant I/O costs during batch update or insert data. Our application has some complex entities. We do batch update (merge detached entity) every 2 minutes. We find the period significant IO costs these days, and disappeared when turn off the batch updating . 1.ObjectDB is in embedded mode. 2.ObjectDB version is 2.3.7 3.Database file size is nearly | |
Auto Date for Creation and Update Hi, is there a way with objectdb to use annotations so that - automatically - the creation Date gets updated once only and the change Date on each change ... ? Kind regards, Thomas tlehmann Thomas Lehmann You may be able to update | |
updating one to many sometimes fails we did setup automated tests for our system and it seams that in around 1 of 100 cases the update of a one to many collection is not working. Definition: @OneToMany(fetch=FetchType.LAZY) @Index ... with the information provided. To ensure reliable updates , the instance must be associated | |
Multiple Collection Fields not update correctly. But when updating (merging existing record) somehow the rotation overrides the position. I | |
Getting Unexpected internal exception when updating entity in MEM db.java:307) at org.vn.radius.cc.server.db.RtDB. Update (RtDB.java:101) ... 10 more Caused by: java.lang | |
Update Entity references if we change the type of an entity will be committed. So after the database update your application can be used with this option | |
Internal exception when updating date filed (TemporalType.DATE) Hello! ObjectDB version 2.5.3_02. I get internal exception when commiting update Date field (javax.persistence.TemporalType.DATE). [ObjectDB 2.5.3_02] javax.persistence.RollbackException Failed to commit transaction: (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:290 | |
Schema Update: class hierarchy change build 2.6.3_02 that should fix this issue. support Support Thanks for the Update . Now it works | |
schema update procedure Is there a specific procedure that we should follow when making schema updates ? I have often found that it takes several restarts of the the server to complete the change. The issue is that there may be changes in many places. Each change appears to be applied as the class is first encountered | |
Indexes broken after schema update. Anyone else noticed this? I updated an entity Object with some new fields, restarted the database to pick up the new schema and now none of the indexes work, except the @Id. I can query by any field that is not indexed on the existing Object but as soon as I try and query against a field | |
Schema-Update: Rename superclass and remove one subclassSchema-Update: Rename superclass and remove one subclass | |
Unable to update a OneToMany SetUnable to update a OneToMany Set | |
NPE after an @embedded obj is updated for a detached entityNPE after an @embedded obj is updated for a detached entity | |
Bidirectional OneToMany is slow on updated itemsBidirectional OneToMany is slow on updated items | |
Is there an update on running ObjectDB purely in-memory?Is there an update on running ObjectDB purely in-memory? | |
Exception after update of indices of Entity classException after update of indices of Entity class | |
Entity object parameter in Explorer parameter Hello, I cannot set an entity object in a parameter for a bulk update in the explorer query ... parameter for an update ? Any time that I need to do a bulk update , I need to compile a special ... the SET clause. For example, in the query: UPDATE Account dep SET dep.status=:a WHERE dep.status=:b | |
Pessimistic Lock Timeouts setting. My situation is where many clients from 1 company are accessing the same counter when bulk ... on stale updates . Willks William Support of pessimistic lock timeout setting ( javax.persistence ... to update object com.x.y.z.ProductCodeTracking:1 - locked by another owner (error 672) And finally | |
Indexes broken after schema update was updated , etc.). support Support I'll dig up the change revision for the entity so I can work | |
Deadlock on Schema Update during Multithreading activityDeadlock on Schema Update during Multithreading activity | |
DB Doctor sets type to "unknown" for new fields and run DB Doctor on the exiting DB file in order to update the schema. The fields are added ... ) is set to unknown. Both are defined as Boolean in Java code. As a result, update operations ... the DB file and for the confirmation that it is Ok. We are struggling to understand then why updates | |
jakarta.persistence.ForeignKey: FOREIGN KEY ( {, } ... ) REFERENCES [ ( {, } ... ) ] [ ON UPDATE ] [ ON DELETE ... will generate foreign key constraints whose update and delete actions it determines most appropriate ... element is not specified, the provider will generate a constraint whose update and delete actions | |
jakarta.persistence.FlushModeType TypedQuery object, the persistence provider is responsible for ensuring that all updates to the state ... this by flushing updates to those entities to the database or by some other means. On the other hand, if COMMIT is set, the effect of updates made to entities in the persistence context on queries | |
jakarta.persistence.Version or timestamp fails during an attempt to update the entity, that is, if the version or timestamp held in the database changes between reading the state of an entity instance and attempting to update or ... ; This field declares a revision timestamp: @Version @Column(name = "LAST_ UPDATED ") private Instant | |
Server closes if large query runs out of memory understand that JPA bulk delete doesn't involve any object retrieval, whereas perhaps JDO deletion does | |
jakarta.persistence.StoredProcedureQuery.getUpdateCount()() Return the update count or -1 if there is no pending result or if the next result is not an update count. Returns: update count or -1 if there is no pending result or if the next result is not an update count. Throws: PersistenceException - if the query execution exceeds the query timeout value set | |
jakarta.persistence.StoredProcedureQuery.executeUpdate()() Return the update count of -1 if there is no pending result or if the first result is not an update count. The provider will call execute on the query if needed. Returns: the update count or -1 if there is no pending result or if the next result is not an update count.. Throws: PersistenceException | |
jakarta.persistence.JoinColumn provider. Default: true Since: Jakarta Persistence (JPA) 1.0 boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider. Default: true | |
jakarta.persistence.MapKeyColumn boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by | |
jakarta.persistence.MapKeyJoinColumn provider. Default: true Since: Jakarta Persistence (JPA) 1.0 boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider. Default: true | |
jakarta.persistence.EntityManager.createQuery(CriteriaUpdate); CriteriaUpdate updateQuery ) Create an instance of Query for executing a criteria update query. Parameters: updateQuery - a criteria update query object Returns: the new query instance. Throws: IllegalArgumentException - if the update query is found to be invalid. Since: Jakarta Persistence (JPA) 2.1 | |
jakarta.persistence.EntityManager.createNativeQuery(String) Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager Query createNativeQuery ( String sqlString ) Create an instance of Query for executing a native SQL statement, e.g., for update or delete. If the query is not an update or delete query, query execution will result | |
jakarta.persistence.ManyToOne = false) @JoinColumn(name = "CUST_ID", nullable = false, updatable = false) public Customer | |
jakarta.persistence.Persistence.PERSISTENCE_PROVIDER.spi.PersistenceProvider" or remove PERSISTENCE_PROVIDER field and also update TCK signature tests. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.CacheStoreMode.USE Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CacheStoreMode USE Insert entity data into cache when read from database and insert/ update entity data when written to the database: this is the default behavior. Does not force refresh of already cached items when reading from database. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.CacheStoreMode.REFRESH Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.CacheStoreMode REFRESH Insert/ update entity data held in the cache when read from the database and when written to the database. Force refresh of cache for items read from database. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TypedQuery.getResultStream() language UPDATE or DELETE statement. PessimisticLockException - if pessimistic locking fails | |
jakarta.persistence.TypedQuery.getSingleResult() Jakarta Persistence (JPA) Method in jakarta.persistence.TypedQuery X getSingleResult() Execute a SELECT query that returns a single result. Returns: the result, of type X . Throws: IllegalStateException - if called for a Jakarta Persistence query language UPDATE or DELETE statement | |
jakarta.persistence.TypedQuery.getSingleResultOrNull() language UPDATE or DELETE statement. LockTimeoutException - if pessimistic locking fails | |
jakarta.persistence.TypedQuery.getResultList() for a Jakarta Persistence query language UPDATE or DELETE statement. PessimisticLockException | |
jakarta.persistence.StoredProcedureQuery.getOutputParameterValue(int) Jakarta Persistence (JPA) Method in jakarta.persistence.StoredProcedureQuery Object getOutputParameterValue ( int position ) Retrieve a value passed back from the procedure through an INOUT or OUT parameter. For portability, all results corresponding to result sets and update counts | |
jakarta.persistence.StoredProcedureQuery.getOutputParameterValue(String) Jakarta Persistence (JPA) Method in jakarta.persistence.StoredProcedureQuery Object getOutputParameterValue ( String parameterName ) Retrieve a value passed back from the procedure through an INOUT or OUT parameter. For portability, all results corresponding to result sets and update | |
jakarta.persistence.StoredProcedureQuery.execute() Jakarta Persistence (JPA) Method in jakarta.persistence.StoredProcedureQuery boolean execute() Return true if the first result corresponds to a result set, and false if it is an update count or if there are no results other than through INOUT and OUT parameters, if any. Returns: true if first | |
jakarta.persistence.StoredProcedureQuery.hasMoreResults() Jakarta Persistence (JPA) Method in jakarta.persistence.StoredProcedureQuery boolean hasMoreResults() Return true if the next result corresponds to a result set, and false if it is an update count or if there are no results other than through INOUT and OUT parameters, if any. Returns: true | |
jakarta.persistence.ForeignKey.value will generate a constraint whose update and delete actions it determines most appropriate for the join column | |
jakarta.persistence.LockModeType.OPTIMISTIC_FORCE_INCREMENT Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.LockModeType OPTIMISTIC_FORCE_INCREMENT Optimistic lock, with version update . Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.LockModeType.PESSIMISTIC_FORCE_INCREMENT Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.LockModeType PESSIMISTIC_FORCE_INCREMENT Pessimistic write lock, with version update . Since: Jakarta Persistence (JPA) 2.0 | |
Explorer bug ? Objects seem to be missing from database in Class view, but are present as references to elementId(1) INFO: RequestBean []: Updated : com.greensoft.entity.Project [1](TEST: project 1) INFO ... ) to elementId(7) INFO: RequestBean []: Updated : com.greensoft.entity.Block [7](TEST: constrained block1, in 1st project) INFO: RequestBean []: Updated : com.greensoft.entity.Constraint [8](TEST: a 1st | |
NullPointerException when using multithreading. Persisting bulk of objects every transaction (instead of a transaction per entity object). support | |
Query on primary key is slow when using 'IN' was also trying to find if there was any API like entityManager.find, but for bulk retrieval by primary keys |