On Sun, Apr 25, 1999 at 06:44:24PM -0500, Jason L Tibbitts III wrote:
> SJS> It seems to me that placing a Majordomo list in a database
> SJS> table may make some administrative tasks easier, but there are
> SJS> probably going to be performance issues too.
>
> I don't see how it would change administrative tasks in the slightest,
> since you still need to do everything from the blessed Majordomo interfaces
> (either email, command line, or through the library) and it's been trivial
> to write code that uses the library interface for some time now. (I've
> done it in more than one instance and there are examples in the
> distribution. I doubt anyone else has played with it, though.)
The main use that springs to mind is the external sourcing of data,
typically from a "larger" user or account database. Maybe some
companies customer account system or the like.
Providing SQL views onto this data in a mj friendly way would save
some real problems with inconsitencies etc.
Regards,
--
Peter Galbavy
Knowledge Matters Ltd
http://www.knowledge.com /http://www.wonderland.org/ http://www.literature.org/
Follow-Ups:
References:
|
|
