[Systers-dev] Mailman thread on MySQL Member Adaptor

[Andrew Grover]

Hi Malveeka,

My understanding of the MembershipAdaptor interface was that it
abstracted all user info from the other Mailman components, enabling
the user datastore to be swapped out without any changes to other
components. You're saying this is not the case?

Your task should be completely independent from Dlists. Your testing
should be against non-Dlist-enabled lists at this point. (Even doing
your work against the base Mailman codebase might make sense.) The key
deliverable is a database-backed MembershipAdaptor, using Storm ORM.
You will likely end up with a Storm db mapper class called Member,
that hides the actual SQL operations from your StormMembershipAdaptor
class.

As you mentioned, the Dlist code stores additional information in the
database for members, lists, and messages. Kanika has been working to
improve this code, and have it also make use of Storm ORM. She will
also end up with Storm db mapper classes for each database table, one
for members, lists, threads, etc, and the functions in DlistUtils will
become member functions of those classes.

There will be a point down the road where both sets of improvements
are made to work with each other, but for now I'd ask to not get hung
up on issues around that, and just focus on the immediate work to be
done.

Regards -- Andy