| _+html-tag attributes|The content will be wrapped with '<html-tagattributes>'. Example: SELECT 'example' AS '_+a href="http://example.com"' creates '<ahref="http://example.com">example</a>' |
| _+<html-tagattributes>|The content will be wrapped with '<html-tagattributes>'. Example: SELECT 'example' AS '_+a href="http://example.com"' creates '<ahref="http://example.com">example</a>' |
| _=varname |The content will be saved in store 'user' under 'varname'. Retrieve it later via {{varname:U}}. See `STORE_USER`_, `store_user_examples`_ |
| _=<varname> |The content will be saved in store 'user' under 'varname'. Retrieve it later via {{varname:U}}. Example: 'SELECT "Hello world" AS _=text'. See `STORE_USER`_, `store_user_examples`_ |
|_<nonReservedName> |Suppress output. Column names with leading underscore are used to select data from the database and make it available in other parts of the report without generating any output. |
* Column names like `_pagee`, `_mailto`, ... are wrapper to class link.
* The parameters for link contains a prefix to make them position-independent.
* Parameter have to be separated with '|'. If '|' is part of the value, it needs to be escaped '\\|'. This can be done via QFQ SQL function `QBAR()` - see `qbar-qscape-qfq-delimiter`_.
Ein Frosch der voller Ueberraschungen war. Ein<spanclass="qfq-more-text"> Frosch der voller Ueberraschungen war. Ein Frosch der voller Ueberraschungen war. Ein Frosch der voller Ueberraschungen war.</span></td>