Bug #52585
closed
Overwriting exiting database during install does not work
Added by Oliver Hader almost 11 years ago.
Updated almost 7 years ago.
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
-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.
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
You might want to install TYPO3 CMS into a not empty DB to e.g. share certain tables with another application.
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.
- 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.
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF