14 | Date field Index is corrupted due to time changeHi, can you shed some light on why we cannot delete data from the attached DB file. A delete ... , so the error message that you got on an attempt to delete objects could happen with other operations as ... in 2.6.4_12 (and of course 2.6.5). The delete query we run is: DELETE FROM RecordingMetaData |
14 | Performance and memory usage of queries requires so much memory. In the implementation of our UnitTests we have used "DELETE FROM Object" to delete ... .setFlushMode(FlushModeType.AUTO); em.getTransaction().begin(); Query q = em.createQuery("DELETE FROM ... mentioning my similar experience. I remember I had an issue several times with deleting many object |
14 | Server closes if large query runs out of memory during JDO deletion query, and the temp threshold was set and was low (64mb). There is an easy work-around, which is to divide up the deletion into smaller number of objects. I understand that JPA bulk delete doesn't involve any object retrieval, whereas perhaps JDO deletion does. Would using JPA for large |
2 | Removed entities can be found by query in the same transaction __odbtracker/m (type STA, value=Persistent-Deleted-Flushed) which shows that the entity is deleted ... what is the problem? best regards BTC btc_es BTC EmbeddedSystems If an entity was deleted from ... at least two different snapshots of objects - one with the deleted object and the other without the deleted object |
2 | ClassCastException thrown when running count query i have inserted. I'm currently evaluating your product. So i insert and delete a lot of data. I ... enforce reference integrity and it is the application responsibility to avoid deletion from the database ... will be produced. support Support The orphan Position records are there because i deleted some Units |
0 | flush()Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active, this method synchronizes the cache with the datastore and reports any exceptions. If an optimistic |
0 | isTransactional(pc) of a makeTransactional method call; newly made persistent or deleted persistent instances; persistent instances read |
0 | flush()Method javax.jdo.PersistenceManager void flush() Flushes all dirty, new, and deleted instances to the data store. It has no effect if a transaction is not active. If a datastore transaction is active, this method synchronizes the cache with the datastore and reports any exceptions. If an optimistic |
0 | jdoIsDirty()Method javax.jdo.spi.PersistenceCapable boolean jdoIsDirty() Tests whether this object is dirty. Instances that have been modified, deleted, or newly made persistent in the current transaction return true. Transient instances return false. Returns: true if this instance has been modified in |
0 | isDirty(pc)Method javax.jdo.spi.StateManager boolean isDirty( PersistenceCapable pc ) Tests whether this object is dirty. Instances that have been modified, deleted, or newly made persistent in the current transaction return true. Transient nontransactional instances return false. Parameters: pc - the calling |
