[rql2sql] closes #1832859: fake HAVING terms w/ EXISTS terms
there are cases where we want to use the HAVING trick on terms that should
belong to an EXISTS subquery. Currently , this causes bad sql. We should fix
that until we've a proper rql grammar avoiding the need for this trick.
Notice at some point, we may want **actuall** HAVING clauses and GROUPBY used
in EXISTS subquery, but that's another story.
CSS Coding Standards
--------------------
(Draft, to be continued)
:Naming: camelCase
Indentation rules
~~~~~~~~~~~~~~~~~
- 2 espaces avant les propriétés
- pas d'espace avant les ":", un espace après
- 1 seul espace entre les différentes valeurs pour une même propriété
Documentation
~~~~~~~~~~~~~
Please keep rules semantically linked grouped together, with a comment about
what they are for.
Recommendation
~~~~~~~~~~~~~~
- Try to use existing classes rather than introduce new ones
- Keep things as simple as possible while in the framework
- Think about later customization by application
- Avoid introducing a new CSS file for a few lines of CSS, at least while the
framework doesn't include packing functionalities