For testing : no migration error on startup, and each group/user directory should have a version 0 in the same database (only for groups/user directories stored in database).
To check this, look in the table Ametys_version, entries like theses should exist :
component_identifier |
ametys_version_number |
execution_date |
execution_comment |
org.ametys.plugins.core.group.directory.Jdbc.upgrade_Groups |
0 |
2020-06-23 18:32:21 |
Automatic Initialization. |
org.ametys.plugins.core.group.directory.Jdbc.upgrade_Groups2 |
0 |
2020-06-23 18:32:21 |
Automatic Initialization. |
org.ametys.plugins.core.user.directory.Jdbc.upgrade_Users |
0 |
2020-06-23 18:05:56 |
Automatic Initialization. |
org.ametys.plugins.core.user.directory.Jdbc.upgrade_Users2 |
0 |
2020-06-23 18:05:56 |
Automatic Initialization. |
In this case, there are 2 user populations and 2 groups in this database, each one have a version associated.
Note : tables are created only when used, so to create one, just try to connect as anything in a group, or search in one.
In fact, this test test the script handler AND RUNTIME-3444
For testing : no migration error on startup, and each group/user directory should have a version 0 in the same database (only for groups/user directories stored in database).
To check this, look in the table Ametys_version, entries like theses should exist :
In this case, there are 2 user populations and 2 groups in this database, each one have a version associated.
Note : tables are created only when used, so to create one, just try to connect as anything in a group, or search in one.
In fact, this test test the script handler AND
RUNTIME-3444