Commit 8d6660ea authored by Carsten  Rose's avatar Carsten Rose
Browse files

Manual.rst: adjustments for 'slaveId' concept.

parent e9c63967
Pipeline #2553 passed with stages
in 2 minutes and 42 seconds
......@@ -1908,7 +1908,7 @@ Store: *VARS* - V
+=========================+============================================================================================================================================+
| random | Random string with length of 32 alphanum chars (lower & upper case). This is variable is always filled. |
+-------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
| slaveId | see *FormElement* `action` |
| slaveId | see `slaveId`_ |
+-------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
.. _`store_vars_form_element_upload`:
......@@ -3126,6 +3126,12 @@ See also at specific *FormElement* definitions.
* `s/d/n`: string or date or number.
slaveId, sqlBefore, sqlAfter, ...
"""""""""""""""""""""""""""""""""
See `slave-id`_
Native *FormElements*
"""""""""""""""""""""
......@@ -3981,7 +3987,8 @@ Requires: *'upload'-FormElement.name* is unknown as a column in the primary tabl
This mode will serve further database structure scenarios.
A typical name for such an 'upload'-FormElement, to show that the name does not exist in the table, might start with 'my', e.g. 'myUpload1'.
A typical name for such an 'upload'-FormElement, to show that the name does not exist in the primary table, might start
with 'my', e.g. 'myUpload1'.
* *FormElement.value* = `<string>` - The path/filename, shown during 'form load' to indicate a previous uploaded file, has to be queried
with this field. E.g.::
......@@ -4357,8 +4364,8 @@ Action
Multi Form
----------
`Multi Forms` are like a regular form with the difference that the shown FormElements are repeated for *each* selected record
(defined by `multiSql`).
`Multi Forms` are like a regular form with the difference that the shown FormElements are repeated for *each* selected
record (defined by `multiSql`).
+------------------+----------------------------------+------------------------------------------------+
......@@ -4369,6 +4376,9 @@ Multi Form
| multiMgsNoRecord | Default: No data | Message shown if `multiSql` selects no records |
+------------------+----------------------------------+------------------------------------------------+
* Multi Form do not use 'record-locking' at all.
The Form is shown as a HTML table.
* `multiSql`: Selects the records where the defined FormElements will work on each.
......@@ -4382,7 +4392,7 @@ Simple
General:
* It's not possible to create new records in simple mode, only existing records can be used.
* It's not possible to create new records in simple mode, only existing records can be modified.
Form:
......@@ -4398,9 +4408,9 @@ FormElement:
Advanced
========
* The `FormElement.name` do not have to be a column of the primary table.
* If `FormElement.name` is not a column of the primary table, the insert/update/delete SQL statement has to be
extra defined.
To handle foreign records (insert/update/delete), use the `slaveId`_ concept.
Typically the `FormElement.name` is not a column of the primary table.
.. _multiple-languages:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment