landsandboat/sql/audit_gm.sql

--
-- Table structure for table `audit_gm`
--

DROP TABLE IF EXISTS `audit_gm`;
CREATE TABLE `audit_gm` (
  `date_time` DATETIME(3) NOT NULL,
  `gm_name` VARCHAR(16) NOT NULL,
  `command` VARCHAR(40) NOT NULL,
  `full_string` VARCHAR(200) NOT NULL,
  PRIMARY KEY (`date_time`,`gm_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
Add capability to log GM command use to database. Functions as a minimum to bother logging, tier zero commands always ignored. Value of 2=log t2 and above but ignore t1. Another approach would have been to add a new field to the cmdprops table however this is re-read each and every time a command is used and would add more overhead reading those in addition to requiring an alteration of every existing GM command script. Doing this entirely core side is the most efficient solution unelss you want to rewrite the commandhandler source. Which we probably could. Changing the table to be a mask would be a lot more efficient as well but far less human readable. 2016-10-04 07:36:33 -04:00			`--`
			-- Table structure for table `audit_gm`
			`--`

			DROP TABLE IF EXISTS `audit_gm`;
			CREATE TABLE `audit_gm` (
Fix Duplicate Key Errors on Audit GM Adds ms precision to GM Command Logging to prevent duplicate key errors when commands from the same character come at the same second. 2025-09-25 13:40:02 -07:00			`date_time` DATETIME(3) NOT NULL,
			`gm_name` VARCHAR(16) NOT NULL,
			`command` VARCHAR(40) NOT NULL,
			`full_string` VARCHAR(200) NOT NULL,
Add capability to log GM command use to database. Functions as a minimum to bother logging, tier zero commands always ignored. Value of 2=log t2 and above but ignore t1. Another approach would have been to add a new field to the cmdprops table however this is re-read each and every time a command is used and would add more overhead reading those in addition to requiring an alteration of every existing GM command script. Doing this entirely core side is the most efficient solution unelss you want to rewrite the commandhandler source. Which we probably could. Changing the table to be a mask would be a lot more efficient as well but far less human readable. 2016-10-04 07:36:33 -04:00			PRIMARY KEY (`date_time`,`gm_name`)
[SQL] Add COLLATE=utf8mb4_general_ci to all tables 2024-01-04 18:25:12 +00:00			`) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;`