Summary of the "subsets_" fields in ListManager

The subsets table stores information about every subset created in the ListManager system. Subsets allow the list administrator to provide the SQL statement that is used to generate the member list for a posting. The SQL statement is broken into several parts in this table to allow it to be recombined in a generic way across multiple database vendors.

Subsets must be attached to a list, but a list may have multiple subsets.

Primary key: SubsetID_

Field Name

Description

Version Added

ClauseAdd_

SQL statements that would be appended to the end of the SQL statement, such as 'group by' or 'having'. Currently unimplement. (text, NULL)

ClauseAfterSelect_

Data to be added to the subset SQL after the select clause. Designed to allow Oracle user to provide a index hint. (text, NULL)

ClauseFrom_

The SQL 'from' line. This is the list of all the tables participating in the SQL statement. (text, NULL)

ClauseOrderBy_

The 'order by' SQL statement. This is for display purposes only. (text, NULL)

ClauseSelect_

The 'select' line of the SQL statement. These are the columns to retrieve. (text, NULL)

ClauseWhere_

The 'where' portion of the SQL statement. Defines the reductions and join rules used to retrieve data. (text, NULL)

Desc_

A short description of the subset. (varchar(90), NULL)

List_

The list that this subset is associated with. (varchar(60), NOT NULL)

MailStreamID The Mail Stream associated with this Segment (int, NULL) 10.0

Name_

The name of the subset. This is used as name-list@server for email postings. (varchar (60), NOT NULL)

NumTestRecords_

The number of records to retrieve when testing the subset. (int, NOT NULL )

AddWhereList_

Should ListManager automatically add the 'where' criteria to restrict this query to the list name that this subset is associated with, or can this subset get to data outside of this list. Default is T, meaning to add the where criteria and keep the subset restricted to the specific list. Setting this to F allows postings to every member on the server, so is very dangerous. (bool)

AddWhereMemberType_

Should ListManager automatically add the 'where' criteria to restrict this query to 'normal' members? Default is 'T'. Normally ListManager would only send to 'normal' members, not to held or unsubscribed or other statuses. Setting this field to 'F' sends to every member type in the system, so is very dangerous. (bool)

AddWhereSubType_

Should ListManager automatically add the 'where' criteria to restrict this query to 'mail' members? Default is 'T'. Normal postings only go to members who want normal 'mail' delivery, not those wanting digest or who have requested not to be sent mail. Setting this field to 'F' allows every member type to be sent to, so is very dangerous. (bool)

SubsetID_

Identifier for the subset. (int, identity, NOT NULL)

Type_

Whether this subset is "normal" or "triggered" (varchar(20), NULL)