Database structure

Please note: This page is under construction and has not been finished yet.

Introduction

Best practices

• Do not modify the core database structure

👍 Use your own tables (for example by creating a plugin) if you want to work with additional data in the database.

• Do not (ab)use database tables and fields for other purposes

👍 Stick to purposes defined in the database tables overview, or create your own database tables

Database prefix

The default database table prefix is e107_ and can be customized by the user during the installation of e107. The prefix that is used on an installation can always be found in the e107_config.php file.

There are several ways the database prefix is used:

1. Recommended: It is strongly recommend to make use of the database methods. Using these methods, the database table prefix is processed automatically.

2. By using the # sign, one can automatically refer to the database prefix. This is generally used when using the e107::getDB()->gen() method, to manually construct an SQL query.

3. In rare cases, you may reference the MPREFIX constant. Its use is deprecated and not encouraged.

Database tables overview

TODO: Finish table below.

The following table provides an overview of all database tables in a clean e107 installation, with their respective purposes.

Table name	Description
admin_log
audit_log
banlist
comments
core
core_media
core_media_cat
cron
dblog
generic	Table for generic purposes. Generally used to store temporary date. Currently also used by welcome message. Developers are discouraged to use this table!
links
mail_recipients
mail_content
menus
news
news_category
online
page
page_chapters
plugin
rate
submitnews
tmp
upload
user
userclass_classes
user_extended