Bug #96406
closed
Do not create invalid sqlite db file names
0%
Description
The Environment check complains about invalid sqlite database file name, which is has been created by the Core.
Updated by Markus Klein over 2 years ago
- Related to Feature #85739: Reduce restrictions on database names introduced for DBAL added
Updated by Markus Klein over 2 years ago
- Related to Feature #85256: Enable SQLite in installation process added
Updated by Gerrit Code Review over 2 years ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/72748
Updated by Markus Klein over 2 years ago
- Status changed from Under Review to New
- TYPO3 Version changed from 11 to 12
Looks like this is not related to the sqlite's filename, but to the internal DB name, sort of.
Debugging the env check reveals the DB name is always an empty string.
I suspect that something is different in v12 now, because I do not recall this an issue with v11
Updated by Benni Mack over 2 years ago
Markus Klein wrote in #note-4:
Looks like this is not related to the sqlite's filename, but to the internal DB name, sort of.
Debugging the env check reveals the DB name is always an empty string.
I suspect that something is different in v12 now, because I do not recall this an issue with v11
Might be related to Doctrine DBAL 3.x?
Updated by Markus Klein about 1 year ago
- Status changed from New to Closed
Can't be reproduced on current v12