Platform
Table of Contents
Namespaces
- Traits
Classes
- MariaDB1010Platform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- MariaDB1052Platform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- MariaDB1060Platform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- MariaDBPlatform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- MySQL80Platform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- MySQL84Platform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- MySQLPlatform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- PlatformHelper
- PlatformInformation
- Helper to handle platform specific details
- PostgreSQLPlatform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
- SQLitePlatform
- doctrine/dbal 4+ removed the old doctrine event system. The new way is to extend the platform
class(es) and directly override the methods instead of consuming events. Therefore, we need to
extend the platform classes to provide some changes for TYPO3 database schema operations.
Traits
- MySQLCompatibleAlterTablePlatformAwareTrait
- `doctrine/dbal` does not support handling engine options directly. This trait in combination with extended
platform classes substitutes the deprecated `doctrine/event-manager` approach to influence database schema
related comparison and DDL handling.