[EMAIL PROTECTED] wrote: > The problem here is that the unique key on the ACL_PERMISSION table is > [Object (the ACL_OBJECT_IDENTITY reference column), Recipient]. It > wouldn't seem from the suggested schema for this table that you can > support different collections for the same Recipient based on the Mask. > > > Is this the case? Is it safe to extend the unique key to include Mask? > Would collection filtering even work if I did?
You just need to use an integer which represents both the "read" and "write" bits being high. You shouldn't need two separate rows. This is whole idea of bit masking in the ACL system - to represent multiple permissions being switched on or off via a single integer. BTW I'd recommend you consider using the new ACL package in 1.0.3. It has a CumulativePermission class which may help. Cheers Ben ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list Acegisecurity-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
