Bug #23575
Allow DBAL to interact with EM to configure remapping
Status: | Resolved | Start date: | 2010-09-21 | |
---|---|---|---|---|
Priority: | Must have | Due date: | ||
Assigned To: | Xavier Perseguers | % Done: | 100% |
|
Category: | DBAL | Spent time: | - | |
Target version: | - | |||
TYPO3 Version: | Is Regression: | |||
PHP Version: | Sprint Focus: | |||
Complexity: |
Description
When using an Oracle DBMS, length of identifiers is limited to 30 characters. DBAL can be configured to automatically remap table and field names to shorter or other ones.
To work, the remapping configuration must be available before the corresponding table has been created.
Idea is that EM triggers DBAL before an extension is installed. This would allow to determine whether remapping should be used (typically if DBMS is Oracle and table/field names longer than 30 characters). In such case, and if the remapping configuration is not already present in localconf.php (if administrator already "prepared" the remapping), it should provide a middle step for the installation where DBAL could propose a mapping configuration to be written to localconf.php.
User should be able to modify the automatic mapping configuration before it is written to localconf.php. After that, EM should go on as usual and show table to be created/fields to be added.
Example of remapping configuration:
$TYPO3_CONF_VARS['EXTCONF']['dbal']['mapping'] = array(
'cachingframework_cache_hash' => array(
'mapTableName' => 'cf_cache_hash',
),
'cachingframework_cache_hash_tags' => array(
'mapTableName' => 'cf_cache_hash_tags',
),
'cachingframework_cache_pages' => array(
'mapTableName' => 'cf_cache_pages',
),
'tx_templavoila_datastructure' => array(
'mapTableName' => 'tx_templavoila_ds',
),
);
(issue imported from #M15755)
Related issues
Associated revisions
History
#1 Updated by Xavier Perseguers almost 5 years ago
Just uploaded some ongoing work to show how this could be done.
#2 Updated by Xavier Perseguers over 4 years ago
Committed to DBAL trunk (rev. 40177)
#3 Updated by Susanne Moog over 4 years ago
- Target version deleted (
4.5.0)
#4 Updated by Xavier Perseguers almost 4 years ago
- Status changed from Closed to New
- Priority changed from Should have to Must have
- TYPO3 Version set to 4.5
This is open again because the corresponding part in EM was removed and refactoring changed the method signature.
#5 Updated by Xavier Perseguers almost 4 years ago
- Tracker changed from Feature to Bug
- Project changed from Core to DBAL
- Category deleted (
DBAL)
#6 Updated by Mr. Hudson almost 4 years ago
Patch set 1 of change I42e9ab7ed5513bdd031e186592b1768a7a00cedd has been pushed to the review server.
It is available at http://review.typo3.org/4616
#7 Updated by Mr. Hudson almost 4 years ago
Patch set 1 of change I5cb2f78e889f3abfce8e50aa7c455c79e52ad9ce has been pushed to the review server.
It is available at http://review.typo3.org/4617
#8 Updated by Xavier Perseguers almost 4 years ago
- Status changed from New to Under Review
#9 Updated by Xavier Perseguers almost 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
#10 Updated by Michael Stucki over 1 year ago
- Project changed from DBAL to Core
#11 Updated by Michael Stucki over 1 year ago
- Category set to DBAL