Feature #17571
closed
Relation between tables fe_users and fe_groups should be a clean mm relation
Added by Sonja Schubert about 17 years ago.
Updated over 4 years ago.
Sprint Focus:
Needs Decision
Description
Relation between tables fe_users and fe_groups should be a clean mm relation.
The current solution has a lot of disadvantages, ie. if you wanna get all users from a specific group, you can not use a simple select statement. That's a big problem if you have some hundred or even thousands of users.
(issue imported from #M6241)
Would be nice, but a change like that would have compatibility issues. Extensions rely on that structure for both reading and writing.
You can use FIND_IN_SET in your WHERE clause, but in any case you will have to do many requests, because of subgroups :)
I understand that this is a big change, but isn't there a plan to 'clean up' the core from such things, or to provide some api workaround for the old extensions so that it would be easy to adapt them.
- Target version deleted (
0)
Any news or plan about this issue?
Thanks
- Description updated (diff)
- Sprint Focus set to PRC
- Category deleted (
Database API (Doctrine DBAL))
- Status changed from New to Closed
hey sonja. thanks for the suggestion. you're still correct here, be_user to be_groups and the same for fe_users to fe_groups sholud be modeled as true mm relation. however, currently nobody is actively working in this area and having the issue open for some further years does not really help us.
thus, i'll now close the issue: doing this major change will need a concept, active people working on it and a series of dedicated preparation, doing and migration issues. this generic issue does not help us much in this transition, so i'm closing it for now. hope this is ok.
- Sprint Focus changed from PRC to Needs Decision
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by