Bug #3564
database warnings on postVarSets
| Status: | Rejected | Start date: | 2009-06-04 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
When the query on the lookup table returns no result, a php database warning is thrown.
Sample configuration of a postVarSet:
'product' => array(
array(
'GETvar' => 'tx_monierproduct_single[id]',
'lookUpTable' => array(
'table' => 'tx_monierproduct_mainproduct',
'id_field' => 'uid',
'alias_field' => 'title',
'addWhereClause' => ' AND NOT deleted AND pid=3171',
'useUniqueCache' => 1,
'useUniqueCache_conf' => array(
'strtolower' => 1,
'spaceCharacter' => '-',
),
),
),
),
so when there's no matching title on the given pid, the mySQL result is empty and a warnings are thrown.
Associated revisions
[Bug 3564] For the CSV export of registrations and events, use localized column headings,r=oliver
[Bug 3564] For the CSV export of registrations and events, use localized column headings,r=oliver
[Bug 3564] For the CSV export of registrations and events, use localized column headings,r=oliver
History
Updated by Daniel Poetzinger almost 4 years ago
- Status changed from New to Rejected
this seems to be related to realurl