Merge branch 'develop' into F15098_AS_function_in_variable

.readthedocs.yml

@@ -5,6 +5,12 @@
 # Required
 version: 2
 
+# Set the OS, Python version and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.12"
+
 # Build documentation in the docs/ directory with Sphinx
 sphinx:
   configuration: Documentation/conf.py
@@ -14,8 +20,7 @@ formats:
   - pdf
   - epub
 
-# Optionally set the version of Python and requirements required to build your docs
+# Requirements to build your docs
 python:
-  version: 3.7
   install:
     - requirements: Documentation/docker-sphinx-qfq/requirements.txt
\ No newline at end of file

Documentation/GeneralTips.rst

@@ -292,3 +292,30 @@ The FE User record (table: fe_users)
   * Has to be assigned to a T3 page ``fe_users.pid``.
   * The T3 page has to be configured as ``record store`` on the T3 Plugin login box.
   * Access time has to be zero or a currently valid period.
+
+MariaDB
+-------
+
+Row size too large
+^^^^^^^^^^^^^^^^^^
+
+* Details: https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/
+* Typically too many columns per table on an InnoDB Table.
+* First try is to check (and to change) ROW_FORMAT: ::
+
+    ALTER TABLE tab ROW_FORMAT=DYNAMIC;
+
+* Bad workaround for creating a wide table: ::
+
+    SET SESSION innodb_strict_mode=OFF;
+    CREATE TABLE ...
+
+* Best is to change as much columns as neccessary from ``varchar()`` to ``tinytext`` / ``text``
+
+SQL Dump with one record per line
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Sometimes it's helpful to have SQL dumps with each record on a single line::
+
+    msyqldump --skip-opt <DB-Name>
+

Documentation/Report.rst

@@ -345,8 +345,8 @@ Text across several lines
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
 To get better human readable SQL queries, it's possible to split a line across several lines. Lines
-with keywords are on their own (:ref:`QFQ Keywords (Bodytext)<qfq_keywords>` start a new line). If a line is not a 'keyword' line, it will
-be appended to the last keyword line. 'Keyword' lines are detected on::
+with keywords are on their own (:ref:`QFQ Keywords (Bodytext)<qfq_keywords>` start a new line). If a line is not a
+'keyword' line, it will be appended to the last keyword line. 'Keyword' lines are detected on::
 
     <level>.<keyword> =
     {

Documentation/conf.py

@@ -55,7 +55,7 @@ master_doc = 'index'
 # General information about the project.
 project = 'QFQ'
 copyright = '2023'
-author = 'Carsten Rose, Benjamin Baer'
+author = 'Carsten Rose, Benjamin Baer, Enis Nuredini, Jan Haller'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the

Documentation/docker-sphinx-qfq/requirements.txt

-sphinx-rtd-theme==0.4.3
+sphinx-rtd-theme
 git+https://github.com/readthedocs/readthedocs-sphinx-search@main

extension/ext_emconf.php

@@ -7,7 +7,7 @@ $EM_CONF['qfq'] = array(
     'title' => 'Quick Form Query',
     'description' => 'Framework to build web applications: Form (dynamic), report, typeahead, multi language, link protection, PDF, send mail (dynamic attachments, PDFs), multiple databases, record locking, secure up/download.',
     'category' => 'fe',
-    'author' => 'Carsten Rose, Benjamin Baer',
+    'author' => 'Carsten Rose, Benjamin Baer, Enis Nuredini, Jan Haller',
     'author_email' => 'carsten.rose@math.uzh.ch',
     'dependencies' => 'fluid,extbase',
     'clearcacheonload' => true,