Commit 7b1eae8a authored by Carsten  Rose's avatar Carsten Rose
Browse files

Manual.rst: fix some typos'.

Makefile: remove automatically downloaded file.
parent 23bbe1f1
Pipeline #860 passed with stage
in 1 minute and 40 seconds
...@@ -33,7 +33,8 @@ update-qfq-doc: ...@@ -33,7 +33,8 @@ update-qfq-doc:
cd ../qfq-doc/; \ cd ../qfq-doc/; \
git commit -a; \ git commit -a; \
git push git push
wget https://docs.typo3.org/~mbless/github.com/T3DocumentationStarter/Public-Info-053.git.make/request_rebuild.php wget -O /tmp/request_rebuild.php https://docs.typo3.org/~mbless/github.com/T3DocumentationStarter/Public-Info-053.git.make/request_rebuild.php
rm /tmp/request_rebuild.php
git-revision: make-dist-dir git-revision: make-dist-dir
......
...@@ -787,13 +787,13 @@ Base: T3 & QFQ ...@@ -787,13 +787,13 @@ Base: T3 & QFQ
QFQ typically interacts with one database, the QFQ database. The database used by Typo3 is typically a separate one. QFQ typically interacts with one database, the QFQ database. The database used by Typo3 is typically a separate one.
Theoretically it might be the same (never tested), but it's strongly recommended to use a separated QFQ database to have Theoretically it might be the same (never tested), but it's strongly recommended to use a separated QFQ database to have
no problems on Typo3 updates and to have a clean separation between Typo3 and QFQ no problems on Typo3 updates and to have a clean separation between Typo3 and QFQ.
QFQ: System & Data QFQ: System & Data
'''''''''''''''''' ''''''''''''''''''
QFQ itself can be separated in 'QFQ system' (see `system-tables`_) and 'QFQ data' databases (>=1). The 'QFQ system' stores QFQ itself can be separated in 'QFQ system' (see `system-tables`_) and 'QFQ data' databases (even more than one are
the forms, record locking, log tables and so on - `QFQ data` is for the rest. possible). The 'QFQ system' stores the forms, record locking, log tables and so on - `QFQ data` is for the rest.
A `Multi Database` setup is given, if 'QFQ system' is different from 'QFQ data'. A `Multi Database` setup is given, if 'QFQ system' is different from 'QFQ data'.
...@@ -811,7 +811,7 @@ in `indexQfq`. If specific forms or reports should use a different database than ...@@ -811,7 +811,7 @@ in `indexQfq`. If specific forms or reports should use a different database than
A `Form` will: A `Form` will:
* load the own definition from `indexQfq` (table `Form` and `FormElement`), * load the form-definition from `indexQfq` (table `Form` and `FormElement`),
* loads and save data from/in `indexData` (config.qfq.php) / `dbIndex` (form.parameter.dbIndex), * loads and save data from/in `indexData` (config.qfq.php) / `dbIndex` (form.parameter.dbIndex),
* retrieve extra information via `dbIndexExtra` - this is useful to offer information from a database and save them in a * retrieve extra information via `dbIndexExtra` - this is useful to offer information from a database and save them in a
different one. different one.
...@@ -862,7 +862,7 @@ Different QFQ versions, shared database ...@@ -862,7 +862,7 @@ Different QFQ versions, shared database
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
When using different QFQ versions and a shared 'QFQ data'-database, there is some risk of conflicting When using different QFQ versions and a shared 'QFQ data'-database, there is some risk of conflicting
'QFQ system' tables. Best is to always use the same QFQ version on all instances ot use a Multi Database setup. 'QFQ system' tables. Best is to always use the same QFQ version on all instances or use a Multi Database setup.
.. _debug: .. _debug:
......
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