Hi Gauthier,
I'm not aware of any workaround.
If you have time, and don't find a workaround, it would be great if you
could maybe put together a simple test case, and add the issue to JIRA.
Thanks,
Richard
--------------------------------------------------
From: "Gauthier Segay" <[email protected]>
Sent: Saturday, January 23, 2010 10:29 PM
To: "nhusers" <[email protected]>
Subject: [nhusers] using Future and multiple queries having same
parametername
I'm using Future<T> and FutureValue<T> with hql queries.
I've encountered exceptions because multiple queries are using the
same parametername, the same exception that you would have using
session.CreateMultiQuery and adding many queries with parameter set on
individual queries (and common parameter name).
As the code grow, I'm not sure I would be able to keep track of
parameter name of queries that may be batched from multiple sources
before being enumerated/resolved.
Is there an existing or planned way to circumvent this behaviour in
multiquery / future without putting this work on the client end of the
API?
Thanks for your feedback
--
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"nhusers" 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/nhusers?hl=en.
