SQL database - Revision history

Uwe: /* Configuration of connection timeout */

2026-07-18T17:08:31Z

Configuration of connection timeout

← Older revision		Revision as of 19:08, 18 July 2026
Line 118:		Line 118:

	=== Configuration of connection timeout ===		=== Configuration of connection timeout ===
	Edit the file <code>/etc/mysql/mariadb.conf.d/50-server.cnf</code> and add <code>wait_timeout = 10000</code>.		Edit the file <code>/etc/mysql/mariadb.conf.d/50-server.cnf</code> and add <code>wait_timeout = 10000</code> at the bottom of the <code>[mysqld]</code> block.

			Restart the database afterwards with <code>sudo systemctl restart mariadb</code>.

	This avoids connection timeouts. The application checks this configuration during startup.		This avoids connection timeouts. The application checks this configuration during startup.

			You can verify the change with the SQL command <code>SHOW VARIABLES LIKE '%timeout%';</code>.

Uwe at 17:07, 18 July 2026

2026-07-18T17:07:02Z

← Older revision		Revision as of 19:07, 18 July 2026
Line 119:		Line 119:
	=== Configuration of connection timeout ===		=== Configuration of connection timeout ===
	Edit the file <code>/etc/mysql/mariadb.conf.d/50-server.cnf</code> and add <code>wait_timeout = 10000</code>.		Edit the file <code>/etc/mysql/mariadb.conf.d/50-server.cnf</code> and add <code>wait_timeout = 10000</code>.

	This avoids connection timeouts. The application checks this configuration during startup.		This avoids connection timeouts. The application checks this configuration during startup.

Uwe at 17:06, 18 July 2026

2026-07-18T17:06:46Z

← Older revision		Revision as of 19:06, 18 July 2026
Line 116:		Line 116:
	\| heating \|\| 0:00 \|\| 23:59 \|\| 0		\| heating \|\| 0:00 \|\| 23:59 \|\| 0
	\|}		\|}

			=== Configuration of connection timeout ===
			Edit the file <code>/etc/mysql/mariadb.conf.d/50-server.cnf</code> and add <code>wait_timeout = 10000</code>.
			This avoids connection timeouts. The application checks this configuration during startup.

Uwe: /* Script-based setup of the actuator schedule */

2025-12-31T12:44:58Z

Script-based setup of the actuator schedule

← Older revision		Revision as of 14:44, 31 December 2025
Line 111:		Line 111:
	\|-		\|-
	\| refill \|\| 0:00 \|\| 23:59 \|\| 0		\| refill \|\| 0:00 \|\| 23:59 \|\| 0
			\|-
			\| ventilation \|\| 0:00 \|\| 23:59 \|\| 0
	\|-		\|-
	\| heating \|\| 0:00 \|\| 23:59 \|\| 0		\| heating \|\| 0:00 \|\| 23:59 \|\| 0
	\|-
	~~\| ventilation \|\| 0:00 \|\| 23:59 \|\| 0~~
	\|}		\|}

Uwe: /* Script-based setup of the database */

2025-12-31T12:44:06Z

Script-based setup of the database

← Older revision		Revision as of 14:44, 31 December 2025
Line 95:		Line 95:

	The script checks if the value provided by the user for <code>ventilation_switch_off_temp</code> is lower than the value provided by the user for <code>ventilation_switch_on_temp</code>. If this is not the case, the script repeats the sequence for entering the data.		The script checks if the value provided by the user for <code>ventilation_switch_off_temp</code> is lower than the value provided by the user for <code>ventilation_switch_on_temp</code>. If this is not the case, the script repeats the sequence for entering the data.

			=== Script-based setup of the actuator schedule ===
			Optionally, the user can request to setup a default actuator schedule in the table <code>schedule</code>.

			If there is existing data in the table, the script asks the user if the data shall be erased.

			The script creates the following entries:

			{\| class="wikitable" style="margin:auto"
			\|+ Default actuator schedule
			\|-
			! schedule_type !! start_time !! stop_time !! is_active
			\|-
			\| balling \|\| 0:00 \|\| 23:59 \|\| 0
			\|-
			\| refill \|\| 0:00 \|\| 23:59 \|\| 0
			\|-
			\| heating \|\| 0:00 \|\| 23:59 \|\| 0
			\|-
			\| ventilation \|\| 0:00 \|\| 23:59 \|\| 0
			\|}

Uwe: /* Script-based setup of the database */

2025-12-31T10:48:29Z

Script-based setup of the database

← Older revision		Revision as of 12:48, 31 December 2025
Line 44:		Line 44:

	== Script-based setup of the database ==		== Script-based setup of the database ==
	The repository provides a script which conducts terminal-based communication with the user to fill the database:		The repository provides a script which conducts terminal-based communication with the user to fill the database.

	=== Credentials for script-based setup of the database ===		=== Credentials for script-based setup of the database ===

Uwe: /* Script-based setup of the user data */

2025-12-31T10:48:13Z

Script-based setup of the user data

← Older revision		Revision as of 12:48, 31 December 2025
Line 65:		Line 65:

	The script asks for the password that shall be used for the entry in the table.		The script asks for the password that shall be used for the entry in the table.
	The script stores a <code>bcrypt<code> hash in the column <code>password</code>.		The script stores a <code>bcrypt</code> hash in the column <code>password</code>.


	=== Script-based setup of the Balling dosing configuration ===		=== Script-based setup of the Balling dosing configuration ===

Uwe: /* Script-based setup of the database */

2025-12-31T10:47:57Z

Script-based setup of the database

← Older revision		Revision as of 12:47, 31 December 2025
Line 50:		Line 50:

	The script checks if the provided credentials are valid.		The script checks if the provided credentials are valid.

			=== Script-based setup of the user data ===
			Optionally, the user can setup the user configuration in the table <code>users</code>.

			The script offers the user the possibility to erase all existing user data.

			The script repeatedly asks the user if he wishes to add user data.

			For each entry that is added in the <code>users</code> table, the script asks the name stored in the column <code>name</code>.

			The name must comply with a simple pattern: Only letters a-z and numbers are allowed - no special characters, no space.

			If the name already exists, the script asks the user if he wishes to overwrite the data.

			The script asks for the password that shall be used for the entry in the table.
			The script stores a <code>bcrypt<code> hash in the column <code>password</code>.


	=== Script-based setup of the Balling dosing configuration ===		=== Script-based setup of the Balling dosing configuration ===

Uwe: /* Automatic configuration of the database */

2025-12-31T10:37:36Z

Automatic configuration of the database

← Older revision		Revision as of 12:37, 31 December 2025
Line 43:		Line 43:
	The [[Event-based deletion of old database entries\|event based deletion of old database entries]] needs to be setup by the user.		The [[Event-based deletion of old database entries\|event based deletion of old database entries]] needs to be setup by the user.

	== ~~Automatic configuration~~ of the database ==		== Script-based setup of the database ==
	The repository provides a script which conducts terminal-based communication with the user to fill the database:		The repository provides a script which conducts terminal-based communication with the user to fill the database:

			=== Credentials for script-based setup of the database ===
	Optionally, the user can provide credentials for accessing the database (by default, root privileges allow modification of all MariaDB databases).		Optionally, the user can provide credentials for accessing the database (by default, root privileges allow modification of all MariaDB databases).

	The script checks if the provided credentials are valid.		The script checks if the provided credentials are valid.

	Optionally, the user can setup the ~~balling~~ dosing configuration in the table <code>balling_set_vals</code>.		=== Script-based setup of the Balling dosing configuration ===
			Optionally, the user can setup the Balling mineral dosing configuration in the table <code>balling_set_vals</code>.

	The script offers the user the possibility to erase all existing Balling dosing configuration.		The script offers the user the possibility to erase all existing Balling dosing configuration.

	The user can modify any pump configuration identified by the pump id which ranges from one to four.		The user can modify any pump configuration identified by the pump id which ranges from one to four.

			Alternatively, the user can leave the configuration of a specific pump empty.

	If there is an existing entry in the balling dosing configuration, the script asks the user if he wishes to overwrite this entry.		If there is an existing entry in the balling dosing configuration, the script asks the user if he wishes to overwrite this entry.

			=== Script-based setup of the heating set values ===
			Optionally, the user can setup the heating control in the table <code>heating_set_vals</code>.

			If there is existing data in the table, the script asks the user if the data shall be erased.

			The script asks the user for the temperature value to switch off the heating stored in the column <code>heating_switch_off_temp</code> and the temperature value to switch on the heating stored in the column <code>heating_switch_on_temp</code>.

			The script checks if the value provided by the user for <code>heating_switch_off_temp</code> is higher than the value provided by the user for <code>heating_switch_on_temp</code>. If this is not the case, the script repeats the sequence for entering the data.

			=== Script-based setup of the ventilation set values ===
			Optionally, the user can setup the ventilation control in the table <code>ventilation_set_vals</code>.

			If there is existing data in the table, the script asks the user if the data shall be erased.

			The script asks the user for the temperature value to switch off the ventilation stored in the column <code>ventilation_switch_off_temp</code> and the temperature value to switch on the ventilation stored in the column <code>ventilation_switch_on_temp</code>.

			The script checks if the value provided by the user for <code>ventilation_switch_off_temp</code> is lower than the value provided by the user for <code>ventilation_switch_on_temp</code>. If this is not the case, the script repeats the sequence for entering the data.

Uwe at 10:16, 31 December 2025

2025-12-31T10:16:05Z

← Older revision		Revision as of 12:16, 31 December 2025
Line 42:		Line 42:
	This requires deletion of old entries. MariaDb offers the functionality of event scheduling.		This requires deletion of old entries. MariaDb offers the functionality of event scheduling.
	The [[Event-based deletion of old database entries\|event based deletion of old database entries]] needs to be setup by the user.		The [[Event-based deletion of old database entries\|event based deletion of old database entries]] needs to be setup by the user.

			== Automatic configuration of the database ==
			The repository provides a script which conducts terminal-based communication with the user to fill the database:

			Optionally, the user can provide credentials for accessing the database (by default, root privileges allow modification of all MariaDB databases).
			The script checks if the provided credentials are valid.

			Optionally, the user can setup the balling dosing configuration in the table <code>balling_set_vals</code>.

			The script offers the user the possibility to erase all existing Balling dosing configuration.

			The user can modify any pump configuration identified by the pump id which ranges from one to four.

			If there is an existing entry in the balling dosing configuration, the script asks the user if he wishes to overwrite this entry.