Developers of Sympa

[Guillaume S <address@concealed>]

Hello

A part of users in our community are included in lists via DB request. Some of them use many emails (professionals and private for instance).

As far I understand two problems: 
1) it is not possible to update via the Web API the "external" DB the users preferences  even if the DB request is relatively easy and could be inserted like an include_sql file (having all information to update the DB except of course the user information which should be given as parameter of the request).
2) in the sympa DB the users are identified via theirs email but changing the email you can loose the relation/identity of the person. We add an ID (auto increment unsigned int) and update the key in user_table (maybe not the best table): the primary key is the user Adress and this ID, the key shall be unique. So far a user can have many emails and if he/she is inserted via DB request all his/her emails can be added simultaneously and if he/she change his/her address with the ID it is always possible to found the user with all the right emails.

Concerning the second point: due to the fact that we change the user_table it seams to be impossible to upgrade sympa without effort. For me an ID (as number) is a standard issue in a DB and I don't really understand why it is not the case in sympa.

I hope that these proposals are acceptable and would help.

Best regards 
Guillaume

--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.