Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
typo3
qfq
Commits
4f062fbb
Commit
4f062fbb
authored
Feb 21, 2018
by
Carsten Rose
Browse files
Reformat word 'level' to be unique
parent
89162ba2
Changes
1
Hide whitespace changes
Inline
Side-by-side
extension/Documentation/Manual.rst
View file @
4f062fbb
...
...
@@ -4755,7 +4755,7 @@ be appended to the last keyword line. 'Keyword' lines are detected on:
*
<level>
.
<keyword>
=
* {
*
<level>
[.
<level
]
{
*
<level>
[.
<
sub
level
]
{
Example::
...
...
@@ -4910,7 +4910,7 @@ The line '10.10' will output 'dummy' in cases where there is at least one corres
If there are no addresses (all persons) it reports the person id.
If there is at least one address, it reports 'dummy', cause that's the last stored content.
Example '
L
evel
Key
': ::
Example '
l
evel': ::
10.sql= SELECT p.id AS _pId, p.name FROM Person AS p
10.5.sql = SELECT adr.city, 'dummy' AS _pId FROM Address AS adr WHERE adr.pId={{10.pId}}
...
...
@@ -4918,7 +4918,7 @@ Example 'Level Key': ::
10.10.sql = SELECT '{{10.pId}}'
Notes to the
level
level:
Notes to the level:
+-------------+------------------------------------------------------------------------------------------------------------------------+
| Levels |A report is divided into levels. The Example has levels *10*, *20*, *30*, *30.5*, *30.5.1*, *50* |
...
...
@@ -4952,8 +4952,8 @@ Report Example 1: ::
.. _wrapping-rows-and-columns:
Wrapping rows and columns: Level
keys
--------------------------------
-----
Wrapping rows and columns: Level
--------------------------------
Order and nesting of queries, will be defined with a typoscript-like syntax: level.sublevel1.subsublevel2. ...
Each 'level' directive needs a final key, e.g: 20.30.10. **sql**. A key **sql** is necessary in order to process a level.
...
...
@@ -6272,7 +6272,7 @@ Formatting (i.e. wrapping of data with HTML tags etc.) can be achieved in two di
One can add formatting output directly into the SQL by either putting it in a separate column of the output or by using
concat to concatenate data and formatting output in a single column.
One can use
?
level keys to define formatting information that will be put before/after/between all rows/columns of the
One can use
'
level
'
keys to define formatting information that will be put before/after/between all rows/columns of the
actual levels result.
Two columns
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment