Not to say bad things about clapf (I really like the product as you know) but I would consider the current design almost a bug. So yes; I would say go for it. It is definity a case that I'm dealing with...
Janos SUTO writes:
Dear clapf-users, I am thinking about a slightly incompatible modification of the database schema. Currently the email addresses are stored in the user table. If a user has 4 email addresses, then it results 4 entries for him. The webui passwords are also stored in the user table, so if a single user has 4 entries, then his password is stored at all 4 entries. Though this works without any problem as the webui handles it, it's not an elegant solution, so I think about changing the SQL database schema as follows: mysql> select * from user; +------+-----------+--------------+------------+-----------+ | uid | username | policy_group | password | isadmin | +------+-----------+--------------+------------+-----------+ | 1000 | sj | 1 | xxxxxxxxx | 1 | +------+-----------+--------------+------------+-----------+ | 1001 | xx | 1 | xxxxxxxxx | 0 | +------+-----------+--------------+------------+-----------+ You see, every user has only one entry in the user table, and the email field went to the brand new 't_email' table as follows: mysql> select * from t_email; +---------+--------------+ | uid | email | +---------+--------------+ | 1000 | s...@aaaa.fu | +---------+--------------+ | 1000 | i...@aaaa.fu | +---------+--------------+ | 1001 | x...@aaaa.fu | +---------+--------------+ .... So this is the plan, if the majority of the clapf users accept it. Or if I don't get too much complaints about this schema modification. LDAP users (--with-userdb=ldap) are not affected by this. So I would like you to vote whether you can accept this or not. Best regards, Janos
