[TYPO3-dev] Further development of DBAL

[Andreas Fernandez]

Hello Bernd,

thank you for your reply. That was my first thought, but that would 
bring a heavy breaking change. The new parameter $having must be between 
$groupBy and $orderBy to make sense, but that would break *any* query 
that uses an ORDER or LIMIT statement. IMHO not feasible for the 6.x 
branch. Inserting that parameter in last place could bypass this 
problem, but this suggests that HAVING is inserted after LIMIT.

Andreas

  Am 08.08.2014 08:15, schrieb bernd wilke:
> Am 07.08.14 22:22, schrieb Andreas Fernandez:
>> Hi,
>>
>> some of you may have noticed I'm currently debugging / extending the
>> DBAL extension.
>> There are still a few points that are broken in core, for example the
>> Extension Manager.
>>
>> The EM uses the HAVING statement at certain points which is *not*
>> supported by DBAL
>> at the moment. Also it uses subselects in SELECT which isn't supported
>> neither (but in
>> WHERE it is?). Currently, I trying to teach DBAL to understand the
>> HAVINGs, but it's very
>> complicated because there is no reserved parameter in any exec_*query
>> method, so it
>> could be pre- or appended anywhere (WHERE, GROUP BY, ORDER BY).
>
> what about a new parameter which by default is empty?
>
> > In general, clauses used must be given in exactly the order shown in
> > the syntax description. For example, a HAVING clause must come after
> > any GROUP BY clause and before any ORDER BY clause.
> [1]
>
> all other solutions seems to be an injection or misusage or at least a 
> very dirty workaround.
>
>
> [1] http://dev.mysql.com/doc/refman/5.1/en/select.html
>
>
> bernd