Skip to Content.
Sympa Menu

devel - [sympa-dev] Re: [sympa-users] modifying sympa to support UID

Subject: Developers of Sympa

List archive

Chronological Thread  
  • From: Yonni Edelist <address@concealed>
  • To: Olivier Salaun - CRU <address@concealed>
  • Cc: address@concealed
  • Subject: [sympa-dev] Re: [sympa-users] modifying sympa to support UID
  • Date: Wed, 8 Dec 2004 18:50:05 +0200

hi Olivier,
thanks for answering.
Quoting Olivier Salaun - CRU <address@concealed>:

> Hi Yonni,
>
> I moved this thread to the sympa-dev mailing list that is more appropriate.
>
> Yonni Edelist wrote:
>
> >i'm trying to integrate sympa into an existing users management system.
> >specifically, i want sympa to work with the external system's UIDs instead
> of emails stored in sympa's DB.
> >users with the same uid can change their emails freely (using the external
> system), and still stay the same user. i would like to change sympa so that
> >it'll fetch the user email from the users management system's database,
> based on the uid which is stored in sympa.
> >
> >
> My first impression : it is VERY ambitious to change Sympa's primary key !
ok, that was my initial thought too. i think i'll just try and keep its DB
updated...
>
> >a couple of examples:
> >scenario 1: a message is distributed to a list. some of the list's
> subscribers have uids. i would like sympa to fetch their emails from the
> external db based on their uids.
> >
> >
> >scenario 2: a list editor/owner changes his email address (through the
> external system). i'd like sympa to be able to know that and update its db
> accordingly.
> >
> >
> >i browsed around in sympa's code, to try and see what needs to be changed.
> >i
> found that i might need to change the following functions:
> >List::get_first_user
> >List::update_user
> >List::add_user
> >List::delete_user
> >
> >
> If you only need to map user email addresses to something external at
> distribution time, then it should not be too hard. You've listed the
> right functions.
ok, good. i just want to be sure that these are all the functions.

> >btw: anybody knows what's the difference between 'func' and 'func_db'? (i.e
> 'get_user' and 'get_user_db')
> >
> >
> It comes from a time when only user preferences were stored in a RDBMS :
>
> * func() deals with subscriber_table
> * func_db() deals with user_table
oh, ok. that means that i'll have to change both function types, right?
>
thanks,
Yonni



Archive powered by MHonArc 2.6.19+.

Top of Page