Replay bot

[shacharrr]

No description provided.

[tslashd]

Table for storing the replays:

CREATE TABLE `MapTimeReplay` (
	`player_id` INT(10) NOT NULL,
	`maptime_id` INT(10) NOT NULL,
	`map_id` INT(10) NOT NULL,
	`replay_frames` LONGBLOB NOT NULL,
	UNIQUE INDEX `maptime_id` (`maptime_id`) USING BTREE,
	INDEX `FK1_PID` (`player_id`) USING BTREE,
	INDEX `map_id` (`map_id`) USING BTREE,
	CONSTRAINT `FK1_PID` FOREIGN KEY (`player_id`) REFERENCES `MapTimes` (`player_id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK2_MapTimeID` FOREIGN KEY (`maptime_id`) REFERENCES `MapTimes` (`id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK3_MapID` FOREIGN KEY (`map_id`) REFERENCES `MapTimes` (`map_id`) ON UPDATE NO ACTION ON DELETE CASCADE
);

Unsure whether we should set player_id to reference the Player table instead of MapTimes 🤔

[1zc]

Table for storing the replays:

CREATE TABLE `MapTimeReplay` (
	`player_id` INT(10) NOT NULL,
	`maptime_id` INT(10) NOT NULL,
	`map_id` INT(10) NOT NULL,
	`replay_frames` LONGBLOB NOT NULL,
	UNIQUE INDEX `maptime_id` (`maptime_id`) USING BTREE,
	INDEX `FK1_PID` (`player_id`) USING BTREE,
	INDEX `map_id` (`map_id`) USING BTREE,
	CONSTRAINT `FK1_PID` FOREIGN KEY (`player_id`) REFERENCES `MapTimes` (`player_id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK2_MapTimeID` FOREIGN KEY (`maptime_id`) REFERENCES `MapTimes` (`id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK3_MapID` FOREIGN KEY (`map_id`) REFERENCES `MapTimes` (`map_id`) ON UPDATE NO ACTION ON DELETE CASCADE
);

Unsure whether we should set player_id to reference the Player table instead of MapTimes 🤔

1. We don't need player_id and map_id if we're linking to maptime_id, as that links to a table that has both.
2. replay_frames can be a JSON data type, no need for blobs - would be better as JSON

[tslashd]

Table for storing the replays:

CREATE TABLE `MapTimeReplay` (
	`player_id` INT(10) NOT NULL,
	`maptime_id` INT(10) NOT NULL,
	`map_id` INT(10) NOT NULL,
	`replay_frames` LONGBLOB NOT NULL,
	UNIQUE INDEX `maptime_id` (`maptime_id`) USING BTREE,
	INDEX `FK1_PID` (`player_id`) USING BTREE,
	INDEX `map_id` (`map_id`) USING BTREE,
	CONSTRAINT `FK1_PID` FOREIGN KEY (`player_id`) REFERENCES `MapTimes` (`player_id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK2_MapTimeID` FOREIGN KEY (`maptime_id`) REFERENCES `MapTimes` (`id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK3_MapID` FOREIGN KEY (`map_id`) REFERENCES `MapTimes` (`map_id`) ON UPDATE NO ACTION ON DELETE CASCADE
);

Unsure whether we should set player_id to reference the Player table instead of MapTimes 🤔

1. We don't need player_id and map_id if we're linking to maptime_id, as that links to a table that has both.
2. replay_frames can be a JSON data type, no need for blobs - would be better as JSON

Might as well just add replay_frames column to MapTimes table in that case, no?

[shacharrr]

Table for storing the replays:

CREATE TABLE `MapTimeReplay` (
	`player_id` INT(10) NOT NULL,
	`maptime_id` INT(10) NOT NULL,
	`map_id` INT(10) NOT NULL,
	`replay_frames` LONGBLOB NOT NULL,
	UNIQUE INDEX `maptime_id` (`maptime_id`) USING BTREE,
	INDEX `FK1_PID` (`player_id`) USING BTREE,
	INDEX `map_id` (`map_id`) USING BTREE,
	CONSTRAINT `FK1_PID` FOREIGN KEY (`player_id`) REFERENCES `MapTimes` (`player_id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK2_MapTimeID` FOREIGN KEY (`maptime_id`) REFERENCES `MapTimes` (`id`) ON UPDATE NO ACTION ON DELETE CASCADE,
	CONSTRAINT `FK3_MapID` FOREIGN KEY (`map_id`) REFERENCES `MapTimes` (`map_id`) ON UPDATE NO ACTION ON DELETE CASCADE
);

Unsure whether we should set player_id to reference the Player table instead of MapTimes 🤔

1. We don't need player_id and map_id if we're linking to maptime_id, as that links to a table that has both.
2. replay_frames can be a JSON data type, no need for blobs - would be better as JSON

As for json, the replay data Is really large and json didnt let me just insert it, I needed to use LONGBLOB and to compress as gzip just to add this, I might doing something wrong here