[Systers-dev] Mailman thread on MySQL Member Adaptor

[kanika vats]

Hi Malveeka,
I am sure that Andy Grover will be able to assist you regarding this in a
more perfect manner.As far as I know:
>
>
> What we want is basically a membership adaptor (similar to the one Jennifer
> has talked about int this mail)  in SQL orPOstgresql.
>
 I went through the MysqlMemberships.py given in the link
http://www.orenet.co.uk/opensource/MailmanMysql/ as pointed by Jennifer in
her previous mail .It is dealing with some new entities and database table
"mailman_mysql" that is nowhere defined in the database cutomized by systers
according to their needs in mailman code.So this means If your project(I may
go wrong here because I have very little knowledge about the authentication
project) involves creation of a new database table and defining new entities
then it surely has to be done with Storm ORM.

>
> I believe Kanika and Andy are already working on using the Storm ORM to
> handle the Systers Dlist functionality. I must admit that I am not very
> experienced with databases and have very little knowledge of Storm ORM. So
> the questions that I have may be naive but kindly bear.
>
> I want to know that whether a SQL membership adaptor for handing user
> authentication information would be built over the Storm ORM layer or can be
> handled independantly - as another module?


If it deals with database then yes Storm will surely be involved but as far
as my knowledge,all the database interaction and creation of tables is done
in DlistUtils.py itself,no other file deals directly with database, so
following the existing trend we should aim at handling the SQL membership
adaptor as an independent module leaving the database interaction part to
DlistUtils.py .This may involve some more additions in DlistUtils.py if
situation demands.

>
> What I understand from reading DlistUtils.py is that Mailing Lists form an
> important entity based on which Subscribers/Threads and Messages are
> defined. Even in the MySQL membership adaptor,memebership is defined on the
> basis of lists. (Users can subscribe to different lists using different
> email addresses and have different passwords for different lists in
> mailman). But I did not see Kanika talking about lists on
> http://systers.org/systers-dev/doku.php/orm_database_abstraction. Are
> Mailing lists (mlists) not going to altered with use of Storm?
>
> As I said, I'm no expert of databases, I could be wrong in my understaning
> and I apologize in advance for that. Maybe how mailing lists are handled by
> Mailman is independant of Subscribers/threads etc.
> Storm


Mailing Lists (mlists) are independent,its an independent module and it will
not be altered with use of storm.In mailman every information is originally
stored as pickle files....do not confuse mailing lists implementation part
with the Subscribers,threads that you see in DlistUtils.py.According to me
Systers have extracted all the useful information that they want from the
mailing lists(mlist) and other things and have customized the database
according to their needs,this thing is accomplished by the dynamic lists
functionality that you see as Dlists.

>
>
> As of now, I am planning to start writing a SQL membership adaptor. Since
> the memebership adaptor relies heavily on how lists are handled (mlists), I
> want to know if you plan to use the Storm ORM for database management of
> lists? It'll be great to get feedback from people working on ORM.
>
>
> Thanks
> Malveeka


Really Andy Grover is the right person who can clear your doubts.As I don't
have accurate knowledge and crstal clear undersatnding of the entire mailman
code,if I went wrong somewhere I will be more than happy to get corrected
regarding this.

>
-- 
Best Regards
Kanika Vats