I personally don't see the need for this. As far as I know this has never
been a feature request from a user, either. We already have so many
configuration options, I prefer to add them only when there is a clear
reason or a clear user desire. I don't see either here, personally.
On Tue, Dec 8, 2015 at 12:11 PM Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
wrote:
Since AUTO requires manual synchronization for native queries, maybe
it's
worth adding such a configuration.
http://vladmihalcea.com/2014/08/13/the-dark-side-of-hibernate-auto-flush/
There might be users who choose ALWAYS, especially if they mix Hibernate
with native queries.
What do you think? Should we add a Jira issue for this issue or we should
leave this responsibility to the application layer?
Vlad
On Tue, Dec 8, 2015 at 7:58 PM, Steve Ebersole <steve(a)hibernate.org>
wrote:
> Well if you read closely I said we support it on the
> EntityManager/Session. As far as I know we have never supported that on
> the EntityManagerFactory/SessionFactory.
>
> On Tue, Dec 8, 2015 at 11:50 AM Vlad Mihalcea <mihalcea.vlad(a)gmail.com>
> wrote:
>
>> Hi,
>>
>> I stumble don this question on the forum:
>>
>>
https://forum.hibernate.org/viewtopic.php?f=1&t=1042301
>>
>> I remember there used to be a "org.hibernate.flushMode" configuration
>> property (Steve mentioned this configuration property on SO too):
>>
>>
>>
http://stackoverflow.com/questions/13259677/how-do-i-set-flush-mode-to-co...
>>
>> I checked the code base and it looks like we no longer support it. Was
>> there any reason for dropping this setting?
>>
>> Vlad
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>