About auto

21-30 of 108Refresh
Forum
4

Performance in large transactions

(FlushModeType.AUTO); EntityTransaction transaction = entityManager.getTransaction ... = getEntityManagerFactory().createEntityManager(); entityManager.setFlushMode(FlushModeType.AUTO ... .setFlushMode(FlushModeType.AUTO);   em.getTransaction().begin();   // SLOW   long startTime
JPA Doc
4

GeneratedValue.strategy

Annotation Element javax.persistence.GeneratedValue GenerationType strategy (Optional) The primary key generation strategy that the persistence provider must use to generate the annotated entity primary key. Default value: javax.persistence.GenerationType.AUTO Since: JPA 1.0
JPA Doc
4

javax.persistence.GeneratedValue

key. Default value: javax.persistence.GenerationType.AUTO Since: JPA 1.0
Forum
3

Spring Transactions (@Transactional) within ObjectDB

, because ObjectDB uses FlushModeType.COMMIT by default. Try switching to FlushModeType.AUTO ... is giving issues. Do you know how to FlushModeType.AUTO in ORM.xml we are not doing any annotations ... the EntityManager:     em.setFlushMode(FlushModeType.AUTO); I think I need help here -- I
Forum
3

Visibility of changes in Transaction is not visible to a JPA QL Query

the default is AUTO. In ObjectDB the default is COMMIT (which is more efficient). Yes, changing the Query to FlushModeType.AUTO meant that the added items are 'visible' However if I Query for an Item that I ... which only show the values for all entities if the Query is in AUTO mode?   Thanks > So are there rules for "table
Forum
3

On ensuring ID available after persist

= GenerationType.AUTO)// Explicit for EclipseLink + Oracle or MySQL @GeneratedValue//ObjectDB takes as AUTO public Long getId() { return id; } The javadocs for EntityManager.persist ... also found this in the documentation at http://www.objectdb.com/java/jpa/entity/generated:     Unlike AUTO
Issue
2

new objects not available in mappedBy associations

FlushModeType.AUTO). What does this mean: "Try to refresh the department object" ? How does one refresh ... , and I'll also examine the FlushModeType.AUTO option as suggested. > What does this mean: "Try ... EntityManager? ps: setting FlushModeType.AUTO in the EntityManager resulted in a huge exception
Forum
2

@SequenceGenerator and single id in whole database

strategy is Auto, which causes global ID's per database, not per class?   Yes, that is correct. The generator is ignored when strategy is AUTO (default). Maybe this should be changed and AUTO should use a generator if specified. lwalkowski
Forum
2

Populating entity id before transaction commit

Hi, I have a question about populating auto generated id before transaction commit. We are using ... and IDs would be set on persist rather than on commit. Alternatively you can force early auto ID setting by: Object id = emf.getPersistenceUnitUtil().getIdentifier();   We are using 'Auto' strategy right
Forum
2

Remove a modified entity cause an optimistic lock exception

FlushModeType.AUTO?) Removing the object. Committing the changes. The console application is the same ... (FlushModeType.AUTO);         em.getTransaction().begin();         em.persist(new MyEntity ... and can be demonstrated with a simple console application. In your last post FlushModeType.AUTO is set