Bug #37469
SQL errors are raised, because of non-existing fields
| Status: | Resolved | Start date: | 2012-05-24 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Alex Kellner | % Done: | 0% |
|
| Category: | Backend | |||
| Target version: | - | |||
| Votes: | 0 |
Description
You defined some title fields in your TCA of the fields table that don't exist as physical fields. Unfortunatly it's a bad behaviour to misuse them to show simple labels as your TCA configuration is used in sql queries.
Example: Admin->DB Tools->Raw Query
History
Updated by Stefan Galinski 12 months ago
Unfortunatly I don't know an easy way to fix this, but at least you could add the four fields as real fields to the database with a small datatype. Another possible hack/workaround would be a manipulation with hooks. Maybe this can provide a starting point:
http://lists.typo3.org/pipermail/typo3-dev/2007-October/025750.html
Updated by Alex Kellner 12 months ago
- Category set to Backend
- Status changed from New to Under Review
- Assignee set to Alex Kellner
Updated by Alex Kellner 11 months ago
- Status changed from Under Review to Resolved
Not the best way, but fixed with another four fields - resolved in trunk
validation_title tinyint(2) unsigned DEFAULT '0' NOT NULL, prefill_title tinyint(2) unsigned DEFAULT '0' NOT NULL, marker_title tinyint(2) unsigned DEFAULT '0' NOT NULL, auto_marker tinyint(2) unsigned DEFAULT '0' NOT NULL,