You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the upgrade to mysql 8.4 (running update_mysql.bat in ibex_utils/installation_and_upgrade) I saw the following error regarding the DELIMITER command when it finally ran EPICS\SystemSetup\config_mysql.bat to populate database tables
Acceptance criteria
error does not occur when running config_mysql.bat
Notes
before installing mysql 8.4 see if running config_mysql.bat errors on your existing setup. The delimiter command exists in both 8.0 and 8.4 but is a client side rather than SQL specific command, it looks like it is being passed over to the server when it should not be. This may be because the truncate_event.sql is being run by a source command and so skips some of the features (so we need to set delimiter, source, reset delimiter), but that is a pure guess. It may be when loading sql files as we do the delimiter has to be set a different way such as on command line
planning 106:00 2024/10/31
The text was updated successfully, but these errors were encountered:
During the upgrade to mysql 8.4 (running
update_mysql.bat
inibex_utils/installation_and_upgrade
) I saw the following error regarding the DELIMITER command when it finally ranEPICS\SystemSetup\config_mysql.bat
to populate database tablesAcceptance criteria
config_mysql.bat
Notes
before installing mysql 8.4 see if running
config_mysql.bat
errors on your existing setup. Thedelimiter
command exists in both 8.0 and 8.4 but is a client side rather than SQL specific command, it looks like it is being passed over to the server when it should not be. This may be because thetruncate_event.sql
is being run by a source command and so skips some of the features (so we need to set delimiter, source, reset delimiter), but that is a pure guess. It may be when loading sql files as we do the delimiter has to be set a different way such as on command lineplanning 106:00 2024/10/31
The text was updated successfully, but these errors were encountered: