3 more things:
- I sync'd to cvs and don't see your changes. Got the JAAS ones though.
- What is acl_class for? I don't see it used in your tests.
- I forgot, below is how I have had to model it. I would think it is to
complex for a base implementation but I just wanted you to see what I
must handle for our product. Notice we are using integers instead of
varchar for all acl lookups.
CREATE TABLE acl_object_identity (
id IDENTITY NOT NULL,
object_identity VARCHAR_IGNORECASE(250) NOT NULL,
CONSTRAINT unique_object_identity UNIQUE(object_identity),
FOREIGN KEY (parent_object) REFERENCES acl_object_identity(id)
);
CREATE TABLE acl_object_relationship (
id INTEGER NOT NULL,
parent_id INTEGER NOT NULL,
CONSTRAINT pk_object_relationship PRIMARY KEY (id, parent_id),
FOREIGN KEY (parent_id) REFERENCES acl_object_identity(id),
FOREIGN KEY (id) REFERENCES acl_object_identity(id)
);
CREATE TABLE acl_permission (
acl_object_id INTEGER NOT NULL,
recipient_id INTEGER NOT NULL,
mask INTEGER NOT NULL,
CONSTRAINT pk_object_relationship PRIMARY KEY (acl_object_id,
recipient_id),
FOREIGN KEY (acl_object_id) REFERENCES acl_object_identity(id),
FOREIGN KEY (recipient_id) REFERENCES acl_object_identity(id)
);
> Hi Andres
>
> I just checked into CVS the improvements. The end database schema is
now
> heavily normalised, with plenty of constraints to prevent incorrect
data:
>
> CREATE TABLE acl_object_identity (
> id IDENTITY NOT NULL,
> object_identity VARCHAR_IGNORECASE(250) NOT NULL,
> parent_object INTEGER,
> acl_class VARCHAR_IGNORECASE(250) NOT NULL,
> CONSTRAINT unique_object_identity UNIQUE(object_identity),
> FOREIGN KEY (parent_object) REFERENCES acl_object_identity(id)
> );
>
> CREATE TABLE acl_permission (
> id IDENTITY NOT NULL,
> acl_object_identity INTEGER NOT NULL,
> recipient VARCHAR_IGNORECASE(100) NOT NULL,
> mask INTEGER NOT NULL,
> CONSTRAINT unique_recipient UNIQUE(acl_object_identity,
recipient),
> FOREIGN KEY (acl_object_identity) REFERENCES
acl_object_identity(id)
> );
>
> Do you have any further suggestions/feedback?
>
> Best regards
> Ben
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes
on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source
Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Acegisecurity-developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Acegisecurity-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
