Bug #6911
SQL error when using setOrderings() without matching()
| Status: | Resolved | Start date: | 2010-03-18 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 8 | Estimated time: | 1.00 hour | |
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
Using setOrderings() on a query object without the use of matching() results in the following SQL error.
Example:
$query = $this->createQuery();
return $query->setOrderings(array('lastname' => \F3\FLOW3\Persistence\QueryInterface::ORDER_ASCENDING))->execute();
Will give the following SQL error:
SQLSTATE[HY000]: General error: 1 no such column: d.parent
When adding a $query->matching(), it works as expected.
Tested on alpha7 using the default SQLite.
Associated revisions
[+BUGFIX] FLOW3 (Persistence): Queries using orderings but no constraints now work, fixes #6911.
History
#1 Updated by Karsten Dambekalns over 5 years ago
- Status changed from New to Accepted
- Assigned To set to Karsten Dambekalns
- Start date deleted (
2010-03-18)
#2 Updated by Karsten Dambekalns over 5 years ago
- Target version set to 1.0 alpha 8
- Start date set to 2010-03-18
- Estimated time set to 1.00
#3 Updated by Karsten Dambekalns over 5 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r3993.