Project

General

Profile

Actions

Feature #4398

closed

Use established lists of possible values for suitable columns instead of dynamic enumerations

Added by Radko Krkoš over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Research and analysis
Target version:
Start date:
10/24/2018
Due date:
% Done:

0%

Estimated time:
To be discussed:

Description

Certain columns, such as:
  • Category,
  • Source type,
  • Target type,
  • Node type,
  • CESNET event class,
  • CESNET event severity,

can only contain a well-known set of values. This list must be compiled to allow for #4383. As that is the case, maybe we could replace the dynamic enumeration of present values with the pre-defined set.
RFC - Please discuss. Maybe a different list of columns is applicable. Be advised: it is possible to extend the ENUM data types in PostgreSQL but not to reorder it (without dumping and recreating the whole table - serious downtime).


Related issues

Is duplicate of Mentat - Feature #4383: Consider switching string classification fields to enumsRejectedJan Mach10/19/2018

Actions
Actions

Also available in: Atom PDF