Overwriting exiting database during install does not work
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
[TASK] Show not empty databases in install tool
This patch enables the visibility of all databases the user has access
to but disables the non empty ones from being chosen.
Reviewed-by: Nicole Cordes
Tested-by: Nicole Cordes
Reviewed-by: Thorsten Kahler
Tested-by: Thorsten Kahler
Reviewed-by: Alexander Opitz
Tested-by: Alexander Opitz
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
#2 Updated by Oliver Hader over 6 years ago
Markus Klein wrote:
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
#5 Updated by Ernesto Baschny over 6 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.