We have global tables, customer-specific tables and event-specific tables.
- Global (G) tables exist only once.
- Customer (C) specific tables exist once per customer.
- Event (E) specific tables exist once per event.
- Stronger separation between the data of customers / events.
- Slightly higher data security
- Easier transfer of event data to event specific on-site servers
- Number of tables can grow quickly in an installation
|crm_*||C||Contains CRM data. Table is dynamically created when CRM functionality is activated for the specific customer.|
|domain||G||Domains, as they are connected to RSVP websites.|
|fcustomer||G||Customers, grouping users|
|fcustomer_fuser||G||Assigns customers to users|
|fevset_*||E||All settings for one event|
|xvl*||E||Modification log per guest|
|ygr*||E||Checkin Log per guest|
|zregprocstep*||E||Registration step list - Deprecated|
The * is replaced with the event number / customer number.
|row_id||auto increment record id - unique in this table|
|guest_id||unique identifier of the guest. This table also stores old records (logging): Whenever a guest is saved, a new record with the same guest id is created. The old record remains stored, so that the entire history of each record is stored.|
|booked_with_guest||Refers to the column id. Value is 0 for the main guest and the id of the main guest for guests who have booked together with the main guest. new in version 1.0.586|