Bug #96406
closed
Do not create invalid sqlite db file names
Added by Markus Klein almost 3 years ago.
Updated over 1 year ago.
Description
The Environment check complains about invalid sqlite database file name, which is has been created by the Core.
- Related to Feature #85739: Reduce restrictions on database names introduced for DBAL added
- Related to Feature #85256: Enable SQLite in installation process added
- Status changed from New to Under Review
- 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
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?
- Status changed from New to Closed
Can't be reproduced on current v12
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by