Project

General

Profile

Actions

Feature #25739

closed

Make mysqldump files install tool compatible

Added by Rens Admiraal about 13 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2011-04-04
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

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

config.yaml (725 Bytes) config.yaml Xavier Perseguers, 2011-04-07 22:29
dump.php (2.53 KB) dump.php Xavier Perseguers, 2011-04-07 22:29

Updated by Xavier Perseguers about 13 years ago

Actions #2

Updated by Xavier Perseguers about 13 years ago

  • File deleted (export.zip)
Actions #3

Updated by Michael Stucki over 10 years ago

  • Project changed from 329 to TYPO3 Core
Actions #4

Updated by Michael Stucki over 10 years ago

  • Category set to 999
Actions #5

Updated by Mathias Schreiber about 9 years ago

  • Target version set to 7.5
Actions #6

Updated by Morton Jonuschat over 8 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?

Actions #7

Updated by Rens Admiraal over 8 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

Actions #8

Updated by Alexander Opitz over 8 years ago

  • Status changed from Needs Feedback to Closed
  • Target version deleted (7.5)

Thanks for Feedback.

I'm closing this issue now.

Actions

Also available in: Atom PDF