Hello

I see that alot modules (Forum for example) that store their roles in the database in next the manner: "Registered Users;" Doesn't the integrity of the database come in danger? Say i make a role "Test" I assign the role to the Forum and then delete it within DotNetNuke ? The string stays there till the next update. And for the sake of space why store it in as string and not as an Id ? Is this because the import/export feature ?

Currently I'm designing my own module, and in my ERD design i have a link table (M:N) between my main module table and the DotNetNuke Role table (i also implemented foreign key's). I normalized the Design and the Rle1;Role2;Role3 does not fit in this picture.

| ID       |   RoleID         | Name               |

Frankly the entire roles system is a bit of a mess - as of 4.4.1

- Im kinda hoping that come 4.5 we will see some much needed cleanup in this area.

Having spent a whole lot of time messing around inside the roles area - database norminalisation is only a small part of things ...

The bigger problem as I see it currently is the caching issues that lead to stupid situations like the USER.Roles() propertly never being hydrated UNLESS you are looking at the current logged on user - and then only AFTER the signin page has redirected.

Or the fact that you cannot change the roles a user is assigned - while that user is logged on.
Currently - a user much log off - and physically log back on BEFORE any roles changes are reflected into the menu items that are displayed and the pages that a user can access.

Westa

Once I finally get to the bottom of the key issues

- then I will be doing just that -

Westa