Project

General

Profile

Actions

Feature #4383

closed

Consider switching string classification fields to enums

Added by Pavel Kácha almost 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Development - Core
Target version:
Start date:
10/19/2018
Due date:
% Done:

30%

Estimated time:
To be discussed:

Description

Currently at least Category, *.Type, Severity and Class are stored as strings. Changing them to enums might gain us

  • space reduction
  • performance (very likely)
  • possibility of GIN index
  • possibility of range queries ("gimme everything from Abusive.Spam to Abusive.Violence", i.e. "all under Abusive")

Warden does it in a similar way:
warden:source:warden3/warden_server/catmap_mysql.json
warden:source:warden3/warden_server/tagmap_mysql.json


Related issues

Has duplicate Mentat - Feature #4398: Use established lists of possible values for suitable columns instead of dynamic enumerationsClosedRadko Krkoš10/24/2018

Actions
Blocked by Mentat - Feature #4230: Make use of existing or implement own mechanism for handling SQL schema migrations.ClosedPavel Kácha07/27/2018

Actions
Actions

Also available in: Atom PDF