[Mailman-Developers] SQL MemberAdaptor implementation?
Thu, 15 Aug 2002 19:39:27 -0400 (EDT)
OK--I think I've found the time to build this and contribute it to the
Just want to make sure that none already exists...
Has anyone built such a beast?
Are there *any* other known implementations to use as references besides
I'm also wondering about dynamic groups... (and think that I should
be able to implement this using some combination of the "virtual" list and
the "extended" list.)
In the system that I'll be integrating this there are several types of
entities, and a dynamic number of instances of each. I'd like to be able
to have each instance of each entity have it's own (probably virtual)
mailing list. The first idea is to create one concrete mailman list (with
settings/templates/etc.) for each type, and have each instance
automagically exist with distinct membership (as pulled from the SQL DB).
As a more concrete example, I might want to set up a "class" mailing list
and a "project" mailing list, but I really want it to appear that there
are many mailing lists all of the form "firstname.lastname@example.org",
"project+noFNORDs@dom.ain", etc. (The plus'es are a straw-man, it could
be deliniated some other way--the key is that I want them each to have a
distinct email address so that people can respond to the group if
desired--if this were announce-only I could simply use the virtual list
and .inject() method.)
Any suggestions as to how to go about this?
I'm guessing I'll make an SQL DB framework that is only mostly concrete.
Each list would need an extend.py that informs that framework about the
schema through which to find various pieces of information in the DB.
Any suggestions as to how that schema should be specified?
This brings up something about which I'm not so clear--can different lists
use different MemberAdaptors? Can I have a single mailman instance
running some lists with OldStyle and other lists using my new fangled