Feature Wiki
Tabs
Database
Page Overview
[Hide]1 General
Maintainer and Tester
Additional
Roadmap
Short Term
Put Database under Coordinator-Model
The goal is to put the Database under the Coordinator-Model. The service is crucial for the whole system and should not be managed by a single person.
Hand out the Database through the Component Bootstrap
Today the component provides ILIAS\Database\Connection as a lazy proxy of ilDBPdo
(ReflectionClass::newLazyProxy()), whose initializer returns $GLOBALS['DIC']->database(). The connection
itself is still built outside the component, by ilInitialisation::initDatabase() via
ilDBWrapperFactory::getWrapper(IL_DB_TYPE).
The goal is that the component builds and hands out the connection itself:
Database.phptakesILIAS\Environment\Configuration\Installation\ClientIniand derives both the driver details (InnoDBDetails/GaleraDetails) and the credentials from it, instead ofIL_DB_TYPEandilDBPdo::initFromIniFile()reading$DIC['ilClientIniFile']. That interface already exposesgetDatabaseType(),-Host(),-User(),-Password()and-Name(); only a getter fordb.portis missing.- The initializer of the lazy proxy then connects that
ilDBPdoinstead of reaching into$DIC,$DIC['ilDB']becomes a plain binding inAllModernComponents, andilInitialisation::initDatabase()is emptied.
Two properties of the lazy proxy have to be kept in mind until then:
- The initializer must return an instance of exactly
ilDBPdo; a subclass or a test double registered as$DIC['ilDB']fails with aTypeErroron first use.ilDBWrapperFactory::getWrapper()always returns anilDBPdotoday. - A lazy object initializes on property access, not on method entry. Methods of
ilDBPdothat do not touch a property run on the uninitialized instance.
One constraint shapes the final solution: the bootstrap reader executes the closures at build time
(Component/src/Dependencies/Reader.php), so nothing may connect there. ilDBPdo::__construct() only takes
its Details and does not connect, so the object can be built at build time as long as connect() happens on
first use, which is exactly what the lazy proxy provides.
Setup keeps its own path: ilDatabaseSetupAgent builds a connection from the data an installer enters, before
any client ini exists.
Mid Term
Narrow the contract other components consume
Connection inherits the complete legacy surface of ilDBInterface. The components that have been migrated
to the bootstrap so far (AccessControl, Filesystem, Logging, ResourceStorage) call a small part of it, and four
methods carry most of the traffic: quote, query, manipulate and fetchObject. Schema manipulation,
which makes up a large part of the surface, belongs to setup and update steps, not to a component asking for
rows.
The goal is a small, driver-agnostic contract for reading and writing rows that Connection narrows down to,
so no builder or mapper has to reimplement the full legacy interface.
Reduce the number of consumers
Around 2400 call sites still reach the database through $DIC->database() or $DIC['ilDB'], and roughly 450
signatures type against ilDBInterface. Each component that gets revised is an opportunity to convert its own
share to an injected dependency; there is no separate project that could do this centrally.
Project: Establish Referential Integrity
Currently (ILIAS 8) ILIAS doesn't use advanced database-built-in functionalities that ensure the integrity of stored data.
The benefits ILIAS demands from the Database Management System (DBMS) regarding data value correctness on field-level currently are:
- uniqueness, by primary or unique indexes
- 'not null' (without a defined default) for essential required fields
- low-level datatype warranty on field-level, reasonable for numeric- and date/time-types, sometimes poor for unspecific varchar fields (examples: email and client_ip in
usr_data) To improve data quality and to support code maintaining modern DBMSs offer several options ILIAS COULD use:
Referential Integrity (Foreign Keys)
- Stored Procedures & Functions
- Trigger
For more information visit the project page: Project: Establish Referential Integrity
Long Term
Query-Builder and and ORM
The goal is to implement a Query-Builder and an ORM or move to a framework which provides these features such as Doctrine.
The narrowed contract described under Mid Term is the precondition: as long as components consume the full
ilDBInterface, no builder or mapper can be put underneath them without reimplementing that surface.
2 Projects
The following projects are planned or have been realised for this component:
NEW Projects
- …
Ongoing Projects
- …
Projects On-Hold
- …
Completed Projects
- …
3 Suggested Features
In the following list you can add a request for a new feature or pick-up an already suggested feature about that should be decided again. The lists below show existing suggestions and scheduled features of this component.
- …
Ready for Jour Fixe
- …
Already suggested
4 Accepted Features
The following features have been accepted for trunk but are not yet scheduled for a specific ILIAS version.
- …
5 Scheduled Features
The following features have been scheduled / published in ILIAS 12:
- …
The following features have been scheduled / published in ILIAS 11:
- …
The following features have been scheduled / published in ILIAS 10:
- …
The following features have been scheduled / published in ILIAS 9:
The following features have been scheduled / published in ILIAS 8:
The following features have been scheduled / published in ILIAS 7:
- …
The following features have been scheduled / published in ILIAS 6:
- …
The following features have been scheduled / published in ILIAS 5.4:
The following features have been scheduled / published in ILIAS 5.3:
- …
The following features have been scheduled / published in ILIAS 5.2:
The following features have been scheduled / published in ILIAS 5.1:
- …
The following features have already been developed and published in ILIAS 5.0:
- …
The following features have already been developed and published in ILIAS 4.4:
The following features have already been developed and published in ILIAS 4.3:
The following features have already been developed and published in ILIAS 4.1:
The following features have already been developed and published in ILIAS 4.1:
- none
The following features have already been developed and published in ILIAS 4.0:
6 Redundant and Rejected Feature Requests
Requests that are redundant (already implemented in other requests)
Rejected Feature Requests
- …
Last edited: 13. Aug 2025, 15:47, Gruber, Ann-Christin [acgruber]