Emmanuel, I understand that would be the ideal. However, even there the
Session-local setting works. You'd just set the Cache Mode prior to
calling multiLoad and then reset it afterwards. So the question is how
worthwhile the separate CacheMode per multiLoad call versus cluttering the
API
On Thu, Nov 5, 2015, 7:01 AM Emmanuel Bernard (JIRA) <
jira(a)hibernate.atlassian.net> wrote:
Emmanuel Bernard
<
https://hibernate.atlassian.net/secure/ViewProfile.jspa?name=emmanuel>
*commented* on [image: Bug] HHH-7572
<
https://hibernate.atlassian.net/browse/HHH-7572> Re: Develop API for
load-by-multiple-ids <
https://hibernate.atlassian.net/browse/HHH-7572>
I guess the question is whether setting that at the Session-level prior to
make this call is sufficient or if there should be a way to pass the
CacheMode in to these methods.
Steve Ebersole
<
https://hibernate.atlassian.net/secure/ViewProfile.jspa?name=steve> in
Hibernate Search case, that's the latter, we receive an already opened
Session so a per method setting would be our use case.
[image: Add Comment]
<
https://hibernate.atlassian.net/browse/HHH-7572#add-comment> Add Comment
<
https://hibernate.atlassian.net/browse/HHH-7572#add-comment> This
message was sent by Atlassian JIRA (v7.0.0-OD-08-005#70107-sha1:5fb2f7e) [image:
Atlassian logo]
_______________________________________________
hibernate-issues mailing list
hibernate-issues(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-issues