Michele,
IIRC, XmlIn is limited to SQL 2005.
I would rather have a more generic approach.

On Wed, Oct 8, 2008 at 6:19 PM, Michele Cantelli <[EMAIL PROTECTED]>wrote:

>  This is the patch for the PermissionsService, now the XmlIn criterion is
> used to match the UsersGroups.
>
> To work with this it's required my previous patch for XmlIn:
> http://groups.google.com/group/rhino-tools-dev/browse_thread/thread/bd81c176ee84e382
> .
>
>
>
> *Da:* [email protected] [mailto:
> [EMAIL PROTECTED] *Per conto di *Ayende Rahien
> *Inviato:* lunedì 6 ottobre 2008 12.24
> *A:* [email protected]
> *Oggetto:* [rhino-tools-dev] Re: Rhino.Security and SQL Server 2100
> parameters limit
>
>
>
> Michele,
> It almost certainly would be accepted. But note that a better alternative
> might be to turn it into XmlIn query if it detects that.
> I have a couple of posts about this issue.
> Another option might be to turn that in into a sub select, but we need to
> test the performance of ti
>
> On Mon, Oct 6, 2008 at 11:45 AM, Michele Cantelli <[EMAIL PROTECTED]>
> wrote:
>
> Working with Rhino.Security and I found a limit  when using SQL Server as
> DBMS: if a user is contained in more than 2,100  UsersGroups NHibernate
> throws SqlException:  "The incoming tabular data stream (TDS) remote
> procedure call (RPC) protocol stream is incorrect. Too many parameters were
> provided in this RPC request. The maximum is 2100."
>
>
>
> I identified the problem in the PermissionsService where a query with
> Expression.In("UsersGroup", usersGroups) is generated.
>
> Googling about this SQL Server issue I see a lot of ppl who face this
> problem splitting the query and batching the execution, anyway I don't think
> that a patch like this for the PermissionsService would be accepted, right?
>
>
>
>
>
>
>
>
>
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" 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/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to