Project

General

Profile

Actions

Bug #52585

closed

Overwriting exiting database during install does not work

Added by Oliver Hader over 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Category:
Install Tool
Target version:
Start date:
2013-10-07
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

It sounds nice that existing data cannot be overwritten anymore... however, if it's intended and the database user is not allowed to create new databases, then one is lost after the first 10 seconds with TYPO3.

Steps to reproduce:
  • install TYPO3 CMS 6.2
  • use user that has a database with data/tables
  • you won't find the database in the list of "empty databases" - which is correct of course, but not helpful

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #49162: Rewrite install toolClosed2011-10-30

Actions
Actions #1

Updated by Markus Klein over 10 years ago

-1 here.

A user usually has access to the database in another way (phpMyAdmin), at least I don't know a single hosting service that does not provide such an access.
The user can clean the DB there.

Actions #2

Updated by Oliver Hader over 10 years ago

Markus Klein wrote:

-1 here.

A user usually has access to the database in another way (phpMyAdmin), at least I don't know a single hosting service that does not provide such an access.
The user can clean the DB there.

Well, I know a lot of them - and this is the origin of this issue as well

Actions #3

Updated by Philipp Gampe over 10 years ago

You might want to install TYPO3 CMS into a not empty DB to e.g. share certain tables with another application.

Actions #4

Updated by Christian Kuhn over 10 years ago

And how to handle a 'partly' filled database? Drop those tables the instance need? What about existing content rows? I'm also in favor of not allowing this, lets discuss this tomorrow, Oli.

Actions #5

Updated by Ernesto Baschny over 10 years ago

  • Assignee set to Christian Kuhn
  • Target version set to 6.2.0

We discussed this in the release team today and decided that we will show the empty databases in the list where the user has access too, but leave them "unselectable" (maybe with a warning beside it = "Not empty") so that he at least has a chance to notice where the error is before wondering if there are permission issues in his DB setup.

Actions #6

Updated by Gerrit Code Review over 10 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24668

Actions #7

Updated by Gerrit Code Review over 10 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/24668

Actions #8

Updated by Nicole Cordes over 10 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #9

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF