Below is near-final. Rendering caveats still apply. Comments on content are welcome. -= -= -= -= -= -= -= -= <h1 id="operators_parse_affecting_attributes"><span>2. </span>Operators, Parse-Affecting Attributes</h1> SQLite understands these operators, listed in precedence<sup>1</sup> order (highest to lowest): <p> </p><table width="80%" border="1" border-collapse="collapse" line-height="1.2"> <tr align="center"> <th width="45%" scope="col" text-align="center">Operators<sup>2</sup></th> <th width="35%" scope="col" text-align="left">Traits<sup>3</sup></th> </tr> <tr align="center"> <td>~ [expr] + [expr] - [expr]</td> <td align="left">·(·x), unary prefix</td> </tr> <tr align="center"> <td>[expr] COLLATE (collation-name)<sup>4</sup></td> <td align="left"> unary postfix</td> </tr> <tr align="center"> <td>||</td> <td align="left">(x·y)·z, binary </td> </tr> <tr align="center"> <td>* / %</td> <td align="left">(x·y)·z, binary</td> </tr> <tr align="center"> <td>+ -</td> <td align="left">(x·y)·z, binary</td> </tr> <tr align="center"> <td>&  | <<  >></td> <td align="left">(x·y)·z, binary</td> </tr> <tr align="center"> <td>ESCAPE [expr]</td> <td align="left"> unary postfix<sup>5</sup></td> </tr> <tr align="center"> <td> < > <= >= </td> <td align="left">(x·y)·z, binary</td> </tr> <tr align="center"> <td>= == <> != IS IS NOT<br> [expr] BETWEEN [expr] AND [expr]<sup> </sup><br> IN MATCH LIKE REGEXP GLOB<sup> </sup><br> [expr] ISNULL [expr] NOTNULL [expr] NOT NULL </td> <td align="left">(x·y)·z, binary<br> (x·y)·z, ternary <sup>6</sup><br> (x·y)·z, binary <sup>6</sup><br> unary postfix</td> </tr> <tr align="center"> <td>NOT [expr]</td> <td align="left"> unary prefix</td> </tr> <tr align="center"> <td>AND</td> <td align="left">(x·y)·z, binary</td> </tr> <tr align="center"> <td>OR</td> <td align="left">(x·y)·z, binary</td> </tr> </table> <p> <b>1.</b> Operators shown within the same table cell share precedence.<br> <b>2.</b> "[expr]" denotes operand locations for non-binary operators.<br> <b>3.</b> "x·(y·z)", "(x·y)·z" and similar denote associativity.<br> <b>4.</b> The COLLATE clause (with its collation-name) acts as a single postfix operator.<br> <b>5.</b> This suffix can only bind to a preceding [expr] LIKE [expr] expression.<br> <b>6.</b> Each keyword in (BETWEEN IN GLOB LIKE MATCH REGEXP) may be NOT-prefixed with the same precedence and associativity. </p>