[Fwd: Re: majordomo and MySQL]

Once again I didn't pay attention to the To: on my reply.
<sigh>
Sean

-------- Original Message --------
Jørn Dahl-Stamnes wrote:
> On Monday 03 December 2007 23:30, Daniel Liston wrote:
>> Are you asking a majordomo question or a SQL question?  What benefit do you
>> gain by storing the mailing list in two places?  I am sure you already see
>> the down side of how much extra time it takes retrieving data from the SQL
>> container, only to write it where and how majordomo would have written it
>> natively.
>>
>> To someone with only a hammer, everything looks like a nail.
> 
> Because I have a place where people register themself as a user (ref. 
> http://www.dahl-stamnes.net/Stmbk/) and I wish to make a list where some 
> users shall be allowed to send emails to all registered users. When they are 
> registered as a user they are automatically in the list.
> 
> A user may change his profile (which contain both a primary and a secondary 
> e-mail adresse) and I want majordomo to use the adresses stored in the SQL 
> database.
> I know that other mailing lists are able to use SQL databases directly, so why 
> can't majordomo use it?
> 
> Today it works by using a perl script which create the files. But since the 
> script is run by cron, it may cause delays.
> 
What I have done to allow web-based "registration" is have the perl
script send the email to majordomo.  I also have (at times) either 1)
written a log file or 2) updated a database, to capture non-majordomo
related information about the registration, but have passed the
zubzcription on to majordomo via his email interface, and eliminated the
hassle of trying to update or maintain the lists/ file outside the
majordomo environment/process.  This also allows the request to trigger
the confirm, moderation, or any other processes configured for the list
with no effort on my part beyond "composing" and sending the email to
majordomo.
http://aok.net/lists

HTH
Sean