Feature #39190
Additional information for ordering properties
| Status: | Closed | Start date: | 2012-07-23 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Francois Suter | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 1.6.0 | |||
| Votes: | 0 |
Description
The Data Filters contain information about ordering. This is used by the Data Providers to sort the records they return. This is not a trivial task due to TYPO3's overlay mechanism (e.g. it is not possible to do alphabetical ordering on text fields for translations with a SQL query since one is supposed to query the original language and overlay translations afterwards).
Extension "dataquery" tries to be smart about this and guesses if a field is text or number. If it's a number it lets it be applied to the SQL statement. If not, it performs the ordering itself (in PHP) after overlays have been applied. This behavior is sometimes excessive as some number fields (e.g. date/time fields) may be different in translations.
It should thus be possible to override this behavior and in both directions, i.e. be able to force the ordering to be applied on the "source" (e.g. the SQL statement) or by provider itself (in PHP). The information should be in the filter.
I propose adding a property "engine", which would have values "source" or "engine". This must be described in the "tesseract" extension, and applied to "datafilter" (just make sure the property is transmitted properly) and to "dataquery" (for actual handling).
Related issues
| related to Data Filter - Feature #39192: Support new "engine" property for ordering | Closed | 2012-07-23 |
Associated revisions
Added new "engine" property to Data Filter structure and base class, resolves #39190
Added new "engine" property to Data Filter structure and base class, resolves #39190
History
Updated by Francois Suter 10 months ago
- Target version set to 1.6.0
Updated by Francois Suter 10 months ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r64775.
Updated by Francois Suter 10 months ago
- Status changed from Resolved to Closed