Off the top of my head I'd say that the first case will perform slightly better. In the first case OpenJPA will get a single connection to the database, in the second case we'll get two (one for merge, and another for refresh). You could change this behavior with the openjpa.ConnectionRetainMode property, but that might have other implications depending on your application.
Regards, -mike -- View this message in context: http://openjpa.208410.n2.nabble.com/merge-doesn-t-refresh-many-to-one-members-unless-attribute-is-called-explicitly-tp6494445p6500031.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
