Tunnel operators are known in advance, so we are populating the tunnels table in advance, for performance and complexity reasons. (Done in T344499.)
However, the table structure is:
+-----------+---------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-----------+---------------------+------+-----+---------+----------------+ | pkid | bigint(20) unsigned | NO | PRI | NULL | auto_increment | | operator | varbinary(256) | YES | UNI | NULL | | | type | varbinary(5) | YES | | NULL | | | anonymous | tinyint(1) | YES | | NULL | | +-----------+---------------------+------+-----+---------+----------------+
...with the type and anonymous values for each operator not known in advance.
We should ensure that the tunnels table is updated with the correct values in these fields as data is imported/updated. (For the initial populate, they are given the default null values.)