From the bug description:
"When executing an aggregating query, the fieldaliases are used to name the fields in the result (ResultNode).
However the fieldnames in the result are not identical to the fieldaliases, but the fieldaliases converted to lowercase.
Apparently fieldnames are converted to lowercase by the database layer, but this behaviour is not justified and not documented."
I din't understand this bug. It is, as far as I can see, not the storage layer (as the searchqueries do not use the storage layer).
Otoh I also can't find any code that 'changes' aliasses or lower-cases fieldnames.
Is this a database specific problem? I.e. a database returns resultsets with different alias names than given in the query sent?
And what are the exact errors (as in: where do things actually go wrong?)
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
