fix: build enable/disable sql on frontend

This commit is contained in:
Nybkox
2025-01-03 22:57:33 +01:00
parent e73356c8da
commit 1be73d8a4c
5 changed files with 5 additions and 17 deletions

View File

@@ -256,8 +256,6 @@ class Analyser extends DatabaseAnalyser {
contentHash: _.isDate(row.LAST_ALTERED) ? row.LAST_ALTERED.toISOString() : row.LAST_ALTERED,
pureName: row.EVENT_NAME,
createSql: row.CREATE_SQL,
enableSql: row.ENABLE_SQL,
disableSql: row.DISABLE_SQL,
objectId: row.EVENT_NAME,
intervalValue: row.INTERVAL_VALUE,
intervalField: row.INTERVAL_FIELD,
@@ -310,8 +308,6 @@ class Analyser extends DatabaseAnalyser {
contentHash: _.isDate(row.LAST_ALTERED) ? row.LAST_ALTERED.toISOString() : row.LAST_ALTERED,
pureName: row.EVENT_NAME,
createSql: row.CREATE_SQL,
enableSql: row.ENABLE_SQL,
disableSql: row.DISABLE_SQL,
objectId: row.EVENT_NAME,
intervalValue: row.INTERVAL_VALUE,
intervalField: row.INTERVAL_FIELD,

View File

@@ -26,9 +26,7 @@ SELECT
END,
' DO ',
EVENT_DEFINITION
) AS CREATE_SQL,
CONCAT('ALTER EVENT ', EVENT_NAME, ' DISABLE;') AS DISABLE_SQL,
CONCAT('ALTER EVENT ', EVENT_NAME, ' ENABLE;') AS ENABLE_SQL
) AS CREATE_SQL
FROM INFORMATION_SCHEMA.EVENTS
WHERE EVENT_SCHEMA = '#DATABASE#' AND EVENT_NAME =OBJECT_ID_CONDITION
`;