How to use the Systers database

The picture describes what a Systers database in PostgreSQL contains, what the primary keys (here PK) are and which data types it contains. The override table doesn't have a primary key. The databases are only used for dynamic lists and each new list becomes its own database, meaning there are several databases in the Systers system.

The thread table keeps track of the different threads, also known as conversations, of the list. The subscriber table keeps information of the different subscribers. Override is used when a subscriber has (un)subscribed to a particular conversation, primarily it's empty but as soon as someone has made a change in their settings regarding subscription to a thread the table gets filled with this data. The message table contains information of each message send to the list. Aliases is used when a subscriber to a list whishes to be able to send email to the list with other email addresses than the one with which the user is subscribed. The other email addresses, or aliases, are stored in the postgreSQL database. Primarily this table is empty.