- Introduction
- Important Instructions
- Requirements
- Database
- Tables
- change_log
- data_absence
- data_booking
- data_custom_shift
- data_employee
- data_employee_access
- data_employment_period
- data_fixed_shift
- data_group
- data_group_access
- data_holiday
- data_individual_working_time
- data_leave_ban
- data_leave_entitlement
- data_leave_type
- data_membership
- data_modified_shift
- data_note
- data_overtime
- data_shift_cycle
- data_shift_cycle_assignment
- data_shift_cycle_element
- data_shift_cycle_exception
- data_shift_requirement
- data_shift_type
- data_shift_type_restriction
- data_special_period
- data_special_shift_requirement
- data_special_weekday_requirement
- data_surcharge_type
- data_user_setting
- data_user_specification
- data_working_time_model
- data_workplace
- Tables
Database User
A user with the following rights must be created on the database server :
- Creating (CREATE, REFERENCES) a Schichtplaner schedule database
- Querying and editing (SELECT, INSERT, UPDATE) the schedule database
- Creating (CREATE TEMPORARY TABLES) temporary tables
You can create a user using the following commands:
CREATE USER 'spuser'@'3.127.186.43' IDENTIFIED BY 'secret123!' REQUIRE SSL;
GRANT SELECT, INSERT, UPDATE, CREATE, REFERENCES ON `sp_schedule_%`.* TO 'spuser'@'3.127.186.43';
GRANT CREATE TEMPORARY TABLES ON *.* TO 'spuser'@'3.127.186.43';
Notes:
You can choose your own username (here: spuser) and password (here: secret123!).
This information will be stored in the schedule settings.
The self-hosted database is accessed from the application server with the IP address 3.127.186.43.
The name of a schedule database is determined by the application server and always begins with sp_schedule_.
You can test whether a valid connection with the created user is possible in the self-hosting settings of the schedule database.