Handling the reference max size in database in backend requests

[Somebodyisnobody]

In legacyclonk/LegacyClonk#67 we discussed about removing the address limit. @maxmitti noticed, that the maximum size of a record is 64Kb as the database column reference is defined as text in table_structure.sql

league/table_structure.sql

Lines 216 to 220 in ae49dd4

	CREATE TABLE IF NOT EXISTS `lg_game_reference` (
	`game_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
	`reference` text NOT NULL,
	PRIMARY KEY (`game_id`)
	) ENGINE=MyISAM DEFAULT CHARSET=latin1;

Independently of the address limit, the title, the required definitions, the number of players, etc. can also reach the 64K b deliberately maliciously or with no awareness. For example, the addresses are not parsed for validity. A 50,000 digit IPv6 address would be possible.

From operations management perspective (@lluchs), is the behavior of the backend a problem that should or should not be resolved? If so, what steps should be taken to address the issue?