[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.
Javascript Coding Standards
---------------------------
(Draft, to be continued)
:Naming: camelCase, except for CONSTANTS
Indentation rules
~~~~~~~~~~~~~~~~~
- espace avant accolade ouvrante
- retour à la ligne après accolade ouvrante (éventuellement pas
de retour à la ligne s'il y a tout sur la même ligne, mais ce n'est
pas le cas ici.
- no tabs
Documentation
~~~~~~~~~~~~~
XXX explain comment format for documentation generation
Coding
~~~~~~
- Don't forget 'var' before variable definition, and semi-colon (';') after **each** statement.
- Check the firebug console for deprecation warnings
API usage
~~~~~~~~~
- unless intended, use jQuery('container') rather than jqNode('container')
See also
~~~~~~~~
http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml