I've already asked you twice to post your class. You haven't. That provides no context for any comment, and I've already told you why datastore operations are delayed until commit/flush. Why do you think there's a flush() method if you think things ought to go straight to the datastore ?
JPA2 spec page 29 footnote 12. <spec>[12] If the application does not set the primary key attribute corresponding to the relationship, the value of that attribute may not be available until after the entity has been flushed to the database.</ spec> <spec>/** * Synchronize the persistence context to the underlying database. * @throws PersistenceException if the flush fails */ public void flush();</spec> <spec>• If X is a new entity, it becomes managed. The entity X will be entered into the database at or before transaction commit or as a result of the flush operation.</ spec> http://www.datanucleus.org/products/accessplatform/jpa/transaction_types.html#optimistic End. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
