Well, at least I'm hinting at the 'bridge' and taglib frontends for of the query layer then, which AFAIK lack support for this then.
The Informix layer has become notoireously complicated, and even a count() went wrong because bidirectional multilevel steps where translated to UNIONS, so a count() gave more than one result.. I imagine that group by results would be messed up even more complicatedly.
That's true. A union query combines several queries' resultsets to one resultset. I suppose what we want is that the "group by" will be performed on the whole resultset and not on parts of the resultset.
This is what informix can do:
select ... from ... where ... group by ... union select ... from ... where ... group by ...
And this is what we probably want:
select ... from ... where ... union select ... from ... where ... group by ...
I guess we have a problem, don't we?
Regards,
Mark Huijser - Developer EO-Technology
