Feature #25739
closedMake mysqldump files install tool compatible
0%
Description
We use an export script (see attachment) in typo3conf/export to make dumps of specific tables into typo3conf/*.sql files. This way we can for example easily export templavoila tables to another instance of a website.
Problem with DBAL is that the default mysqldump file output can't be imported in the install tool anymore. Even with the extra parameters in the documentation of DBAL it's no fit.
So I extended the script a bit to remove charset declarations (which don't matter in our case anyway), add a DROP TABLE command automatically and remove the backticks in CREATE TABLE definitions.
The actual cleanup methods accepts a file, and writes the cleaned up content back into the same file.
Feel free to use this script if useful.
Files
Updated by Xavier Perseguers over 13 years ago
- File config.yaml config.yaml added
- File dump.php dump.php added
- Assignee deleted (
Xavier Perseguers)
Updated by Michael Stucki almost 11 years ago
- Project changed from 329 to TYPO3 Core
Updated by Morton Jonuschat over 9 years ago
- Category changed from 999 to Install Tool
- Status changed from New to Needs Feedback
Install Tool does not rely on SqlParser / DBAL anymore and uses it's own „SqlSchemaMigrationService”. Has this solved the compatibility problem?
Updated by Rens Admiraal over 9 years ago
I've no idea, I don't use this mechanism anymore. So no clue if the bug (which it is imho) is still valid and don't have the time to check if it would still be valid. Maybe someone who still uses TYPO3 can check it
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
7.5)
Thanks for Feedback.
I'm closing this issue now.