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
In particular this was failing (In SguildGenericDB.tcl):
172 proc UpdateDBStatus { sensorName date sid cid timestamp uid status } {
173
174 global MAIN_DB_SOCKETID
175
176 set tmpDate [clock format [clock scan $date] -gmt true -format "%Y%m%d"]
177 set tableName "event_${sensorName}_$tmpDate"
178 set updateString
179 "UPDATE $tableName SET status=$status, last_modified='$timestamp', last_uid='$uid' WHERE sid=$sid AND cid=$cid"
Wrapping the update in a catch like in proc UpdateDBStatusList stopped the server from crashing (this should probably be done anyway to avoid this) but still causes the autocat status updates to fail until the clock catches up to UTC and the correct event table is created.
The text was updated successfully, but these errors were encountered:
In particular this was failing (In SguildGenericDB.tcl):
172 proc UpdateDBStatus { sensorName date sid cid timestamp uid status } {
173
174 global MAIN_DB_SOCKETID
175
176 set tmpDate [clock format [clock scan $date] -gmt true -format "%Y%m%d"]
177 set tableName "event_${sensorName}_$tmpDate"
178 set updateString
179 "UPDATE
$tableName
SET status=$status, last_modified='$timestamp', last_uid='$uid' WHERE sid=$sid AND cid=$cid"Wrapping the update in a catch like in proc UpdateDBStatusList stopped the server from crashing (this should probably be done anyway to avoid this) but still causes the autocat status updates to fail until the clock catches up to UTC and the correct event table is created.
The text was updated successfully, but these errors were encountered: