[Systers-dev] Moving from Pickle Membership to Store in the Postgresql Database

[Jaideep Khandelwal]

Hi Robin, Malveeka

Sorry for the late reply as I was not online for a day. Q&A leads to healthy
and productive work.


The primary email address is the user name (and we keep both the primary and
> secondary emails in that database)
> I think the password is there too.
> It doesn't have the user options or any syncing with other lists (each list
> has its own database tables).
>
> I'm not sure what you mean by bounce info -- how many times messages have
> bounced?  That's not there.
>
> I think the biggest rethinking is that now we treat all email lists
> separately.  How would the schemas have to change (and what would have to
> change outside the single signon) to have one master copy.
>
>
Now , having a Separate Database for the users joining the lists and the
user information could be done in a manner such if a user 'A' comes to
systers.org mailing lists and join  one lists , after that she joins the
second list then the user's data will be checked in the membership database
that the user with this particular username and emailin address does not get
stored once again for the same credentials , overall avoiding the redundancy
for the data.


> And I think the bounce information (if I'm understanding it correctly)
> needs
> some serious thinking through.  Different applications may have different
> ways they count bounces, so you may not be able to have a single "if it
> bounces this many times, drop them" metric.  And if someone belongs to 10
> systers.org lists, and the system sends out password reminders for each
> list
> (or something similar) and they all bounce due to a temporary problem, we
> wouldn't want to count that as 10 bounces.  So I think you need to think
> through the various pros and cons of keeping bounce information in a
> central
> place vs. for each list.
>
> I would like to have an IRC meeting and have a discussion about this issue.


> An alternative way to do this would be to just have a central table of
> username (primary email) and password, and interpose for each app a method
> where you send the single signon module the login credentials and it sends
> you back valid/invalid.  That seems like a lot less work; what would be the
> value of the additional things you are adding here?
>
> I agree that there is an alternative for storing the data into a central
database , but it would get clumsy  for storing  credentials with the
diffrent lists, rather one common database would be better that will avoid
Redundancy , what IMO is to keep these credentials common and if a user want
to use the previous credential that she used for the first list , them it
could be also used by providing the same credentials to the second. Now the
app could be for many applications like CMS, Wiki , Planets as well .


> And how does your database interact with the MM3.0 database?
>
> That is something that I am about to discuss with  Malveeka

Some more suggestions would be awesome!!

Regards
Jaideep