|
Sender: |
|
Date: |
Fri, 16 Sep 2005 16:53:54 -0500 |
Reply-To: |
|
Content-Transfer-Encoding: |
7bit |
Subject: |
|
From: |
|
Content-Type: |
text/plain; charset=ISO-8859-1; format=flowed |
In-Reply-To: |
<432AEBD8.6804.2545043E@localhost> |
Organization: |
University of Notre Dame |
MIME-Version: |
1.0 |
On 9/16/2005 2:59 PM, Francoise Becker wrote:
>
> You can also have one table per list or several tables, each with
> several lists. I'll agree that it does not provide complete
> flexibility, and your LISTSERV database will not be in 4th normal
> form, but if you use a DBMS that has good support for database
> triggers, you should be able to achieve something that works fairly
> well.
>
Given our current requirements, this would result in the creation and periodic
modification of a very large table, or the periodic creation of a very large
number of tables. Neither option is particularly appealing. Ideally, we should
be able to dynamically identify owners, editors, and subscribers using simple
SQL queries against existing tables. I know of at least one open-source product
which appears to provide this functionality, and we intend to evaluate its
suitability for managing these lists.
--
Paul Russell
Senior Systems Administrator
OIT Messaging Systems Team
University of Notre Dame
|
|
|