Bug #2163
"no such table: namespaces* Exception is misleading
| Status: | Resolved | Start date: | 2008-11-12 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Storage Backend | |||
| Target version: | - |
Description
After typo3cr.db was changed to TYPO3CR.db the file TYPO3CR.db was created and the Exception was thrown because the new DB file has no tables.
A NoSuchDatabaseException or MissingDatabaseException would make more sense before creating just an empty DB file.
Associated revisions
TYPO3CR:
- missing SQLIte database file is now detected, fixes #2163
History
#1 Updated by Karsten Dambekalns over 6 years ago
- Category set to Storage Backend
The error is indeed misleading. But SQLIte simply creates an empty database if you connect and there is no database file, so this is rather an issue caused by the way SQLite behaves. For other databases the message would be more helpful.
#2 Updated by Karsten Dambekalns over 6 years ago
- Status changed from New to Accepted
#3 Updated by Karsten Dambekalns over 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1689.